Supabase Production Project and Database Configuration Create a production Supabase project separate from local/staging. Production schema changes come from version-controlled migrations; the dashboard is not the authoritative migration tool after launch.
Committed Migration job Production DB API release migration → → → Figure 5 - Database changes are part of the release
Production checklist • Review Security Advisor and Performance Advisor findings.
• Use indexes that match measured query patterns and monitor connection usage.
• Plan backups/PITR according to business requirements and database size.
• Restrict who can change production and prefer migrations through CI/deployment workflows.
Connection strategy • Application runtime uses the connection/pool mode appropriate to the always-on NestJS topology.
• Migration tooling should use a connection mode that supports migration operations reliably.
• Do not create one PrismaClient per request; retain the singleton service architecture from earlier phases. Supabase runs the managed platform; TaskFlow still owns query design, indexes, connection behavior, application authorization, and safe production-change practices.
Sources: Supabase Production Checklist, maturity model, and shared-responsibility guidance.
Deployment is the controlled movement of a versioned artifact into a configured runtime with evidence of health and a credible rollback path.
Restate the goal of “Supabase Production Project and Database” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: versioned artifact → production config → runtime → health/smoke test → rollback path. Mark the one boundary this lesson changes.
Inspect the current repository state and record the exact files, route, table, or runtime involved. Avoid creating an abstraction before you can name the existing owner.
Implement the smallest vertical slice. Add one coherent change, run the narrowest verification command, and read the output before continuing.
Connect the slice to TaskFlow’s phase artifact: Staging and production deployment runbooks with release identity, environment matrix, smoke tests, and rollback procedure.. Verify behavior from the outside as a user or API client would.
Create one controlled failure that is safe to reproduce. Predict the symptom first, capture evidence, locate the earliest broken boundary, then fix only that cause.
Close the reference and rebuild or explain the core change from memory. Record what you would monitor or test before trusting the same change in production.
1. Build an immutable artifact.
2. Apply production configuration/secrets.
3. Run compatible migrations.
4. Start the new version.
5. Check readiness and smoke tests.
6. Observe errors/latency.
7. Promote or execute rollback.Do not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.
Separate platform deploy status from application readiness; run smoke tests against real routes and dependencies.
Use expand/contract migrations and keep rollback compatibility explicit before release.
Without copying the final source, create a second small scenario that applies “Supabase Production Project and Database” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Apply database migrations as a controlled release step and document backward-compatibility assumptions.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Rollback plan assumes schema can always be downgraded
Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?
If your explanation is vague, repeat the boundary trace before moving on.Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.