Keep your install up to date with one click per service
Your install runs a pinned, tested version of CRCON; it never changes
underneath you. When we ship an update (a new CRCON release, or an
improvement to the template) every service updates through Railway’s
built-in update flow. Nothing to type, no versions to look up.
Open a CRCON service (start with maintenance), go to
Settings, and under Source click Check for updates. If
there’s a new version, Railway offers to update the service; accept
it.
Every CRCON service has this under Settings, Source
2
Repeat for the other four
Do the same for backend, supervisor, frontend, and
webhooks. Starting with maintenance matters only a little: it
runs the database upgrades, and the others wait for it anyway, so a
different order just takes longer, it never breaks anything.
3
Done when everything shows Online
Database upgrades run automatically during the update; there is
never a manual migration step. Log in as usual once the services
are green.
They’re standard databases pinned to versions CRCON is tested
against. Leave them alone.
Sometimes "an update" changes nothing visible
The same repository also holds this documentation site, so Railway
occasionally offers an update that only contains docs changes.
Accepting it is harmless; it rebuilds the service identically.
Back up before big version jumps
All your data lives in the postgres service’s volume. Railway can
back up a volume from the service’s settings; do that before a
major CRCON version jump, just in case.
Deployed before September 2026?
Older deployments pull the CRCON image directly on the maintenance
and webhooks services, so those two won’t show the update button.
To update them, open each one’s Settings, Source and change the
image tag (for example cericmathey/hll_rcon_tool:v12.2.1) to the
same version the other services run. Or redeploy fresh from the
template and this page applies as written.
