Upgrading

Upgrade Procedure

Option A: Pre-built Image

# Pull the latest image
docker compose pull scanner

# Restart with new image
docker compose up -d

# Run any pending migrations
docker compose exec scanner rails db:migrate

Option B: Built from Source

# Pull latest changes
git pull

# Rebuild the scanner image
docker compose build scanner

# Restart
docker compose up -d

# Run any pending migrations
docker compose exec scanner rails db:migrate

Always run db:migrate after upgrading

Even if a release doesn't mention schema changes, running db:migrate is safe (it's a no-op if there's nothing to migrate) and protects you from silent migration gaps.

Checking the Current Version

docker compose exec scanner rails runner "puts Rails.application.config.version rescue 'unknown'"

Or check the GitHub releases page to see the latest version and release notes.

Before Upgrading

1. Read the release notes — check the Releases page for breaking changes
2. Back up your database — especially before major version upgrades

# Dump the database
docker compose exec postgres pg_dump -U scanner scanner_production > backup_$(date +%Y%m%d).sql

Rollback

If an upgrade causes issues:

# Pin to a specific image version
# Edit docker-compose.yml: image: ghcr.io/0din-ai/scanner:v1.2.3

docker compose up -d

Database rollback is only possible if the migrations are reversible. Most Scanner migrations are written to be reversible, but check the release notes for any exceptions.

Zero-Downtime Upgrades

Scanner's single-process architecture (Puma + Solid Queue in-process) doesn't currently support hot rolling upgrades. Expect a brief restart window (~30 seconds) during upgrades.

For environments requiring zero downtime, deploy a blue-green stack (two separate compose stacks behind a load balancer) and switch traffic after the new stack is healthy.