Upgrades and maintenance
Upgrade safely, protect persistent data, and monitor scanner health.
Use matching backend, frontend, and docs image tags for each JustScan release. Database migrations run during backend startup, so take a PostgreSQL backup before a production upgrade. Treat rollback as a platform recovery decision: a database migration may not be reversible by simply starting an older image.
Back up PostgreSQL and the backend data volume. Preserve the encryption key with the backup because it is required to restore encrypted registry credentials.
Before upgrading, record the running tags, save the backup location, communicate the maintenance window, and decide whether CI should continue as non-blocking. After deployment, monitor backend health at /api/v1/health, scanner health in administration, scan queue activity, notification delivery logs, and audit records. Investigate stale scans before increasing timeouts globally.