Deploy on Fly.io
stromboli’s Fly.io setup is fly.toml at the repository root, plus deploy/fly/setup.sh for the first deploy. It runs:
| Notes | ||
|---|---|---|
the stromboli app |
built from deploy/Dockerfile |
one machine (shared-cpu-1x, 512 MB), never auto-stopped, health check on /healthz |
| Postgres | Fly Managed Postgres or any Postgres you bring | stromboli connects over the private network and runs its migrations on startup |
/healthz pings the database, so a machine that can’t reach Postgres never takes traffic. The machine is never stopped when idle: stromboli receives webhooks and runs health checks on a timer.
Deploy
With flyctl logged in (fly auth login), create a database once:
fly mpg create --name stromboli-db --region ams --plan Basic --org <org>
fly mpg list --org <org> # the cluster ID
Then deploy (app names are global on Fly, pick your own):
FLY_MPG_CLUSTER=<cluster-id> ANTHROPIC_API_KEY=sk-ant-... deploy/fly/setup.sh <app-name> <org>
Use STROMBOLI_DB_URL=postgres://... instead of FLY_MPG_CLUSTER to bring your own Postgres.
The script:
- creates the Fly app, unless it exists
- attaches the database as the
STROMBOLI_DB_URLsecret - generates
STROMBOLI_SECRET_KEYandSTROMBOLI_API_TOKENand setsANTHROPIC_API_KEY - runs
fly deploy --ha=false - prints the secrets it generated. Store them now: Fly can’t show a secret’s value again, and
STROMBOLI_SECRET_KEYmust never change
It is safe to re-run: it never replaces a secret that is already set.
Variables
Plain settings are in [env] in fly.toml: models, investigation limits, machine actions and health checks. They are set to the server’s defaults, except two: machine actions are on (STROMBOLI_ACTIONS_ENABLED=true) and health checks run hourly (STROMBOLI_HEALTHCHECK_INTERVAL=1h). Change them in the file, then deploy.
Secrets are set in Fly, never in the file:
| Secret | |
|---|---|
STROMBOLI_DB_URL |
set by fly mpg attach, or by the script from your URL |
STROMBOLI_SECRET_KEY |
encrypts connector credentials at rest. Never change it after the first deploy: stored credentials could no longer be decrypted |
STROMBOLI_API_TOKEN |
the bearer token for the CLI, the API and webhooks |
ANTHROPIC_API_KEY |
needed for investigations (briefs work without it) |
optional: STROMBOLI_WEBHOOK_TOKEN, other provider keys, SLACK_BOT_TOKEN, SLACK_CHANNEL, SLACK_SIGNING_SECRET, SLACK_APPROVERS |
Set one with fly secrets set KEY=value --app <app-name>. That restarts the machine.
Change the setup
Edit fly.toml, then:
fly deploy --app <app-name> --ha=false
Keep one machine: the health checks run on every machine, and alert dedupe assumes a single instance. --ha=false stops fly deploy from adding a second one.
After deploying
export STROMBOLI_URL=https://<app-name>.fly.dev
export STROMBOLI_API_TOKEN=<the token the script printed>
stromboli connector add loki loki url=https://loki.example.com
Then continue the Quickstart from step 2. Alert webhooks go to https://<app-name>.fly.dev/webhooks/....
To have stromboli investigate the Fly apps of your organization, add a fly connector with a read-only token: it is separate from the app stromboli itself runs in.