Staging Deployment
Seed Verification Runbook
Seed data must remain idempotent and non-destructive. It must not delete user-created data, truncate tables, or seed real customer data.
Use this when you need a repeatable operational procedure.
Seed data must remain idempotent and non-destructive. It must not delete user-created data, truncate tables, or seed real customer data.
Local Verification
pnpm db:seed
pnpm db:seed
pnpm db:seed:verifyStaging Use
Run seed in staging only when explicitly approved for demo/sample review. Use sample/demo data until production data migration is explicitly approved.
Sprint 24 staging demo users are opt-in. To create the role-specific review users, set:
SEED_STAGING_DEMO_USERS=true
SEED_STAGING_DEMO_PASSWORD=<temporary-12-plus-character-password>The seed rejects production environments and short or missing demo passwords. Keep the password in the staging secret store, rotate it after review, and never reuse an employee or production password.
Do not run seed to repair production-like business records. If staging already contains review data, confirm seed behavior is additive/upsert-based before running it again.
Developer Details
- Source
- apps/docs/content/staging-deployment/seed-runbook.md
- Owner
- Platform / Operations
- Status
- Current
- Module
- Staging Deployment
- Related route
- /api/health