Staging Deployment
Staging Deployment Checklist
Sprint 24 assumes the first staging deployment target is a Docker host or VPS running the existing web/docs images behind HTTPS reverse proxying for `https://staging-app.submicrons
Use this when you need step-by-step confirmation before or after an operation.
Sprint 24 assumes the first staging deployment target is a Docker host or VPS running the existing web/docs images behind HTTPS reverse proxying for https://staging-app.submicrons.net. Use the same checklist if the host is replaced by another container platform, but record the platform decision in the staging deployment report.
- Confirm branch and commit intended for staging.
- Confirm CI is green.
- Confirm
.env.stagingexists only in the secret store or deployment host. - Run
pnpm env:check:staging. - Run
node scripts/env-check.mjs staging --file=.env.stagingon the staging host. - Confirm all external sending/sync/payment flags are false.
- Run
pnpm db:generate. - Take a database backup.
- Run migration status.
- Apply migrations with deploy mode.
- Run migration status again.
- Run seed only if demo/sample seed is approved.
- Start/restart web and docs processes.
- Check
/api/health. - Check
/api/ready. - Login with a demo staging account.
- Run smoke tests against staging with
pnpm test:smoke:staging. - Check docs app.
- Check feature flags and disabled integrations.
- Ask a manager reviewer to confirm dashboard reachability.
- Record the deployment result and any follow-up System QA issues.
Developer Details
- Source
- apps/docs/content/staging-deployment/deployment-checklist.md
- Owner
- Platform / Operations
- Status
- Current
- Module
- Staging Deployment
- Related route
- /api/health