FULL_STACK_DEVELOPER_2026_COMPLETE - Phase 08 Secrets and Environment Boundaries
Secrets and Environment Boundaries Keep infrastructure credentials out of source control
A database URL is not "just config" when it contains a password. Its storage location is part of your security design.
Password manager → .env on developer machine → NestJS / CLI process →
The secret should reach the process that needs it without becoming source code.
FULL_STACK_DEVELOPER_2026_COMPLETE - Phase 08 Secrets and Environment Boundaries
The rule NEVER COMMIT
Do not commit a real DATABASE_URL , database password, service-role key, access token or downloaded private credential into Git.
Where Phase 08 stores connection information We will prepare the API directory for a future database URL without using Prisma yet.
# apps/api/.env DATABASE_URL="postgresql://...real value..."
# apps/api/.env.example DATABASE_URL=
Git ignore policy # root or API .gitignore .env .env.* !.env.example
From the repository root, run git check-ignore -v apps/api/.env . You want evidence that Git ignores the file.
PowerShell temporary environment variable For a one-session test, you can set a process environment variable:
$env:DATABASE_URL = "postgresql://..."
# verify only that a value exists; do not echo it in screenshots if ($env:DATABASE_URL) { "DATABASE_URL is set" }
This value disappears when that PowerShell process exits. That makes it useful for temporary testing.
Volume 03 - Database Engineering Book 4 of Phase 08
FULL_STACK_DEVELOPER_2026_COMPLETE - Phase 08 Secrets and Environment Boundaries
Why not put the URL in Next.js?
NestJS server → Database credentials
Direct database credentials belong in trusted server/tool environments, never the browser bundle.
Our architecture routes browser requests through NestJS. The browser should not receive a privileged PostgreSQL connection string. Supabase's Data API has a different browser security model built around public/publishable keys and RLS, but that is not the architecture we are teaching in this phase.
Secret leakage response 1. Assume a committed secret has been exposed even if the repository is private. 2. Rotate/reset the credential. 3. Remove it from current files. 4. Determine whether Git history or CI logs contain it. 5. Do not rely on deleting the latest commit as the only response.
Environment separation preview development -> taskflow-dev database staging -> taskflow-staging database production -> taskflow-prod database
The same code can run against different infrastructure by changing environment configuration rather than editing source files.
Checkpoint
[ ] apps/api/.env contains the private URL.
[ ] apps/api/.env.example documents the name only.
[ ] Git ignores the real file.
[ ] No browser-exposed variable contains the database password.Official references used for this phase (verified 2026-09-17): Supabase Database Overview - https://supabase.com/docs/guides/database/overview Connect to your database - https://supabase.com/docs/guides/database/connecting-to-postgres Connecting with psql - https://supabase.com/docs/guides/database/psql Tables and data - https://supabase.com/docs/guides/database/tables Securing your data - https://supabase.com/docs/guides/database/secure-data PostgreSQL 18 psql - https://www.postgresql.org/docs/18/app-psql.html
Volume 03 - Database Engineering Book 4 of Phase 08
Security work starts with trust boundaries and abuse cases. A feature is incomplete until unauthorized and malformed paths are deliberately exercised.
Restate the goal of “Secrets and Environment Boundaries” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: asset → trust boundary → attacker input → control → verified denial/allow. 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: A Supabase project configured for TaskFlow development with documented connection paths and safe environment variables.. 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.
Threat: authenticated User B changes the URL to User A's task id.
Expected control: API loads the resource scope and denies the action.
Evidence: 403 response + unchanged database row + security-safe log.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.
Return to the nearest observable boundary: input, network, process log, database, or rendered UI. Compare actual evidence with the predicted path.
Change one variable at a time and reproduce the original failure after the fix; otherwise you have correlation, not diagnosis.
Without copying the final source, create a second small scenario that applies “Secrets and Environment Boundaries” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Place connection information in environment files excluded from Git.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Pointing preview environments at production data
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.