This adds the RPM package upload in the release workflow and updates Linux installation instructions. I felt that maintaining multiple sets of instructions in several places is awkward so I propose to simply link to the installation instructions in the docs from the README in the project root.
Another note: Automatic package signing does not appear to work for the RPM package. Apparently this has been implemented but is not enabled by default (see here). For the time being one has to disable GPG key verification for the repo in order to be able to install gram. Not sure what can be done about this since, apparently, it is necessary to set an env var for the Forgejo installation.
This adds the RPM package upload in the release workflow and updates Linux installation instructions. I felt that maintaining multiple sets of instructions in several places is awkward so I propose to simply link to the installation instructions in the docs from the README in the project root.
Another note: Automatic package signing does not appear to work for the RPM package. Apparently this has been implemented but is not enabled by default (see [here](https://codeberg.org/forgejo/forgejo/issues/5776)). For the time being one has to disable GPG key verification for the repo in order to be able to install gram. Not sure what can be done about this since, apparently, it is necessary to set an env var for the Forgejo installation.