Updates and backups
Updating Spitfire means running the install command again: the installer backs up the database first, then pulls the new image; if something goes wrong, --rollback takes you back. The most common loss: the server was rebuilt without a copy of .env, the tests are still there, but saved connection passwords no longer decrypt. So read the backups section before you update.
Updating
How you notice a new release
Every hour the controller asks spitfire.tr whether there is a newer release (it sends only its own version). If there is, admins see the Spitfire X is out banner at the top of every page. How to update opens the right command for this installation (Docker, Windows, Kubernetes, remote runners) with a copy button; Hide for this release closes the banner, while the red Security update banner cannot be hidden.
The License → Version and updates card shows the installed version, the installation type, the last check's result, the Outbound proxy and how to update; Check now checks without waiting.
The Version and updates card on the License page: installed version, installation type, update check and the Check now button
One-click update
Docker installations only, off by default. To turn it on:
~/spitfire/install.sh docker --updater on # to turn it off: --updater offThe choice is kept in deploy/docker/.env as SPITFIRE_UPDATER. With it on, Update now shows on the banner and the card when a new release is out (admins only; every request goes to the audit log).
- Only a separate, small updater container reaches the Docker socket (compose profile
updater); the controller does not. The socket means root on the host, which is why the feature stays off until you turn it on. - The updater only moves to a newer release from the signed release list (
releases.json+ signature). - It waits for running runs to end ("Waiting for N run(s) to end") and no new run starts meanwhile; Cancel withdraws it.
- It downloads the bundle, checks its SHA-256 and runs
install.sh docker --yes: the database is backed up underbackups/, the images are pulled, and the controller is down for a few minutes before it restarts. - If something fails, the UI shows the error, the backup's path and the command
~/spitfire/install.sh docker --rollback <dump>; the output is in theupdates/folder.
Kubernetes/Helm, Windows, a remote Docker daemon (DOCKER_HOST=tcp://…) and --offline installations have no such button; the card describes the update in numbered steps.
Automatic update
With the one-click update on, the card shows the Update automatically when a new release is out switch (off by default; installation admins only). While on, a new release installs without asking, with the same steps as above. A release that failed or was canceled is not tried again; start it with Update now. Every automatic update goes to the audit log as spitfire-auto-update.
Updating step by step
Make sure no run is in progress (the update restarts the controller).
On the controller server run the same command as for the installation (the Docker or the Kubernetes line):
curl -fsSL https://spitfire.sh | bash -s -- docker curl -fsSL https://spitfire.sh | bash -s -- kubernetes --context C --namespace NSOn Windows:
irm https://spitfire.sh/ps | iex. The keys (deploy/docker/.envor thespitfire-secretsSecret) and the data are kept; when the version changes, the database is first backed up as~/spitfire/backups/*.dump(the last 5 are kept;--no-backupskips it).Success check: the green box appears and the License → Version and updates card shows the new version.
Update the runners in other locations too: Runners → Updating runners. The Runners page marks runners on another release with a yellow older release tag.
Rolling back
~/spitfire/install.sh docker --rollback # Kubernetes: install.sh kubernetes --rollbackOn Windows & "$env:USERPROFILE\spitfire\install.ps1" -Rollback. The installer backs up the current database, restores the newest dump under backups/ (or --rollback backups/<file>.dump) and goes back to the release that took it. Changes made after the dump do not come back. Without a terminal, --yes is needed.
Backups and SPITFIRE_SECRET_KEY
The data lives in Postgres, while connection secrets are encrypted with SPITFIRE_SECRET_KEY; back up both together. We suggest the single-file backup (database and keys, encrypted with a passphrase you choose):
Take the backup:
~/spitfire/install.sh docker --backup ~/spitfire-$(date +%F).sfbak # Kubernetes: ~/spitfire/install.sh kubernetes --backup …You are asked for a passphrase (at least 12 characters; for a scheduled job,
SPITFIRE_BACKUP_PASSPHRASE). Keep it apart from the file; without it the backup cannot be opened.Success check, the file is listed:
ls -lh ~/spitfire-*.sfbak
To restore (on this or a new machine), install Spitfire first, then:
ls -lh ~/spitfire-*.sfbak
~/spitfire/install.sh docker --restore ~/spitfire-2026-10-10.sfbakThe current database is backed up to backups/ first, then the backup's data and keys replace it; sign in with the backup's users. A backup of a newer release is refused on an older installation (update first); the target keeps its own Postgres password.
A manual backup needs two things: the keys (on Docker ~/spitfire/deploy/docker/.env, on Kubernetes the spitfire-secrets Secret; copy it to a password vault) and the database (~/spitfire/backups/*.dump, restored with pg_restore; add this folder or the Postgres volume to your own backup system).
If SPITFIRE_SECRET_KEY is lost, stored connection secrets (database, Kafka… passwords) cannot be read and you enter them all again. The TLS identity the controller presents to runners is encrypted with this key too.
Uninstalling
~/spitfire/uninstall.sh docker
~/spitfire/uninstall.sh kubernetes --context C --namespace NS
~/spitfire/uninstall.sh runner # remote runners installed with install.sh runnerWindows: & "$env:USERPROFILE\spitfire\uninstall.ps1" docker or & "$env:USERPROFILE\spitfire\uninstall.ps1" runner.
By default the data (Postgres volume / PVC) and the keys (.env / spitfire-secrets) are kept; install.sh brings everything back. --purge (Windows: -Purge) deletes the database, SPITFIRE_SECRET_KEY and the install folder (logs/ and backups/ included) and cannot be undone; copy any backup you want to keep out of the folder first. The folder stays when another installation lives in it or it is a source checkout; --keep-files (-KeepFiles) keeps it too. Wizard installs and other parts such as runners, Tower, Collector or the OTel agent: Removing what you installed.
Common problems
Symptom: After a reinstall, saved connections no longer work; secrets cannot be read or Test fails.
Cause: SPITFIRE_SECRET_KEY changed (e.g. .env was deleted and the installation redone).
Fix: Put back the .env you backed up and run the installer again; without a backup, enter the secrets again.