Deploy on Railway
stromboli’s Railway setup is infrastructure as code, in .railway/railway.go (the Railway Go SDK). It declares one project with two services:
| Service | Source | Notes |
|---|---|---|
stromboli |
openstatusHQ/stromboli on GitHub, built from deploy/Dockerfile |
healthcheck on /healthz, restarts on failure |
postgres |
Railway Postgres | with its volume. stromboli connects over the private network and runs its migrations on startup |
/healthz pings the database, so a deploy that can’t reach Postgres never takes traffic.
Deploy
With the Railway CLI logged in (railway login):
ANTHROPIC_API_KEY=sk-ant-... deploy/railway/setup.sh # optional argument: the project name, default stromboli
The script:
- creates the Railway project, unless this directory is already linked to one
- runs
railway config apply - generates
STROMBOLI_SECRET_KEYandSTROMBOLI_API_TOKEN, setsANTHROPIC_API_KEY, and redeploys - generates the public
*.up.railway.appdomain
It is safe to re-run: it never replaces a secret that is already set.
Deploying a fork? Change the repo in railway.Github(...) first.
Variables
| Variable | In railway.go |
|
|---|---|---|
STROMBOLI_DB_URL |
reference to postgres’s DATABASE_URL |
|
PORT |
8080 |
the port the public domain routes to |
STROMBOLI_SECRET_KEY |
railway.Preserve() |
encrypts connector credentials at rest. Never change it after the first deploy: stored credentials could no longer be decrypted |
STROMBOLI_API_TOKEN |
railway.Preserve() |
the bearer token for the CLI, the API and webhooks |
ANTHROPIC_API_KEY |
railway.Preserve() |
needed for investigations (briefs work without it) |
railway.go declares every variable the server reads, grouped: required, models and provider keys, investigation limits, machine actions, health checks and Slack. Plain settings (STROMBOLI_MODEL, STROMBOLI_MAX_TOOL_CALLS, STROMBOLI_ACTIONS_ENABLED…) are literals, mostly set to the server’s defaults: change them in the file, then railway config apply. Three differ from the server: machine actions are on (STROMBOLI_ACTIONS_ENABLED=true), health checks run hourly (STROMBOLI_HEALTHCHECK_INTERVAL=1h) and post an all-clear to Slack when every service is healthy (STROMBOLI_HEALTHCHECK_SUMMARY=true). Secrets (STROMBOLI_WEBHOOK_TOKEN, the other LLM keys, SLACK_*) are railway.Preserve().
railway.Preserve() keeps the value stored in Railway, so secrets never land in git and railway config apply never touches them. An optional secret stays unset until you set it with railway variable set KEY --stdin --service stromboli.
Change the setup
Edit .railway/railway.go, then:
railway config plan # preview
railway config apply
Railway doesn’t read .railway/ during deploys. Pushing to main redeploys the code, but configuration changes only take effect on railway config apply.
After deploying
export STROMBOLI_URL=https://<your-app>.up.railway.app
export STROMBOLI_API_TOKEN=$(railway variable list --service stromboli --kv | sed -n 's/^STROMBOLI_API_TOKEN=//p')
stromboli connector add loki loki url=https://loki.example.com
Then continue the Quickstart from step 2. Alert webhooks go to https://<your-app>.up.railway.app/webhooks/....