Circuit Breaker runs database migrations automatically on startup — no manual migration steps are required.
cb versionOr in the UI: Settings → About.
If you installed natively with install.sh or via the Proxmox LXC helper (cb-proxmox-deploy.sh), upgrade with:
cb updateThis pulls the latest release, restarts the systemd service, and runs migrations automatically.
For Proxmox LXC: SSH into the container first, then run cb update:
ssh root@<container-ip>
cb updateOr from the PVE host:
pct exec <CTID> -- cb update- Database — all your hardware, services, networks, scans, topology data
- Vault key — encrypted credentials remain readable
- Uploads — custom icons and branding assets
- App settings — auth config, SMTP, OAuth providers, theme preferences
cd ~/.circuitbreaker
docker compose pull
docker compose up -dOr use cb update if the cb CLI is installed.
Named Docker volumes preserve all data between container recreations:
| Volume | Contents |
|---|---|
backend-data |
Database, vault key, uploads |
caddy_data |
Caddy TLS certificates |
nats_data |
NATS state |
postgres_data |
PostgreSQL data (if using --profile pg) |
Edit docker-compose.yml to set a version tag:
image: ghcr.io/blkleg/circuitbreaker:backend-v0.2.0Then:
docker compose up -dcb versionOr check Settings → About in the UI.
Re-run the installer with a specific version tag:
CB_VERSION=v0.1.4 curl -fsSL https://raw.githubusercontent.com/BlkLeg/CircuitBreaker/main/install.sh | bashEdit docker-compose.yml to reference the previous image tag, then:
docker compose up -dReview the release notes before rolling back to check for irreversible schema changes.
- Backup & Restore — recommended before major upgrades
- cb CLI Tool —
cb updateandcb versionreference