Fix release signing script argument handling and checksums
The release-candidate guard read
if [ rcstring != "" ]; then
which compares the literal word "rcstring" against the empty string and is
therefore always true. Final releases took the rename branch too, where it
became a no-op rename of each archive onto itself.
The version and RC suffix were also hardcoded to the previous release, so
the script had to be edited before every use.
Take both as arguments, rename only when there is a suffix to add, and skip
an archive that has already been renamed so a re-run after a failure is not
confusing.
Two other changes:
- Require the signing key to be named through ROLLER_SIGNING_KEY, and refuse
a key that is not RSA or is under 4096 bits. Older keys may still be in a
release manager's keyring and would otherwise be picked by default.
- Write checksums with shasum(1) rather than "gpg --print-md", so downloaders
can verify with "shasum -c", and emit SHA-512 alongside SHA-256.
Claude-Session: https://claude.ai/code/session_019R1jdtwkaYEeA6L9DXEtEi
Apache Roller is a Java-based, full-featured, multi-user and group-blog server suitable for blog sites large and small. Roller is typically run with Apache Tomcat and MySQL. Roller is made up of the following Maven projects:
The Roller Install, User and Template Guides are available in ODT format (for OpenOffice or LibraOffice):
Hit the Roller Confluence wiki:
If you want to run Roller in production, then you should down load the latest official release and install it by following the Installation Guide, which you can find at the documentation link: https://github.com/apache/roller/tree/master/docs.
You probably should not run Roller in production using this technique, but it‘s a relatively easy way to try Roller for yourself. Assuming you’ve got a UNIX shell, Java, Maven and Git:
Get the code:
$ git clone https://github.com/apache/roller.git
Compile and build Roller:
$ cd roller $ mvn -DskipTests=true install
Run Roller in Jetty with an embedded Derby database (for testing only):
$ mvn jetty:run
Once Jetty is up and running browse to http://localhost:8080/roller to try to Roller.
Another way to try Roller is to use Docker. This is actually easier than running via Maven because you do not need Maven or Java. If you‘ve got Docker, here’s how you can run Roller for demo purposes.
Get the code:
$ git clone https://github.com/apache/roller.git
Run Docker Compose to build and launch Roller along with a PostgreSQL database:
$ cd roller $ docker-compose up
It will take a while to build and start the Docker image. Once it's done browse to http://localhost:8080/roller to try Roller.