Variables you set at deploy time
All three live on the backend service; the supervisor references them from there.
Changing them later: edit them on the backend, then redeploy the
backend and supervisor.
Variables you might change later
Multi-server identity
These two make each game server’s data distinct. Rules and per-server values are covered in the multi-server guide.The wiring (don’t touch)
Everything else exists to point services at each other and mirror upstream’s compose file:- Database:
HLL_DB_*on the backend and supervisor reference the Postgres service’s generated credentials (POSTGRES_USER,POSTGRES_PASSWORD,POSTGRES_DB) and private domain. - Redis:
HLL_REDIS_HOST,HLL_REDIS_PORT, andHLL_REDIS_URLreference the Redis service’s private domain. - Secrets:
RCONWEB_API_SECRETis generated once at deploy and encrypts sessions and stored passwords. Never change it after first deploy; doing so invalidates stored credentials. - Cross-service:
CRCON_API_HOST(frontend to backend),SUPERVISOR_RPC_URL(backend to supervisor), andCRCON_FRONTEND_HOST(backend’s internal alias for the UI’s multi-server registry) are all private-network references. - Ports:
PORTtells Railway which port to healthcheck where a healthcheck exists;RCONWEB_PORT,PUBLIC_STATS_PORT, andPUBLIC_STATS_PORT_HTTPSare display-only on Railway. - Logging:
LOGGING_LEVEL(INFO),LOGGING_PATH, andCONFIG_DIRmirror upstream defaults.