How this Forgejo instance is set up and run on Railway
https://code.ravensaqw.com
| forgejo.env | ||
| LICENSE | ||
| README.md | ||
OpenAQW Code
This is how code.ravensaqw.com is set up and run. It is Forgejo, a self-hosted forge, running from Forgejo's official container image on Railway.
There isn't much custom here. If you want your own Forgejo on Railway, this is a reasonable place to start.
What runs
- One Railway service using the image
codeberg.org/forgejo/forgejo:15.0.9, limited to 0.5 vCPU and 0.5 GB of memory. - A Railway volume mounted at
/data. It holds the repositories, the SQLite database, avatars and Forgejo's ownapp.ini. - Railway serves HTTPS and forwards to Forgejo on plain HTTP, port 3000.
code.ravensaqw.comis a CNAME to Railway, set to DNS only in Cloudflare.- There is no SSH. Clone and push over HTTPS, signing in with an access token.
- Sign-ups are closed. Actions are off for now.
Settings
When the container starts, Forgejo's image writes every variable named
FORGEJO__section__KEY into app.ini. forgejo.env lists the
ones set on the Railway service. When one changes, change it in Railway and
here together.
The secret keys and the admin account were made by Forgejo's installer on
first start. They live only in app.ini and the database on the volume, so
they are not in this repository.
Upgrading
- Read Forgejo's release notes for every version between ours and the new one.
- Back up the volume in Railway.
- Change the image tag on the Railway service, and in this README.
- Deploy, then check the site and a
git clone.
License
MIT, see LICENSE.