Skip to content
d3 Wiki
09.01

Supabase project setup and configuration

Every Supabase project starts the same way and is findable.

Updated
Oct 3, 2026
On this page

Purpose

Every Supabase project starts the same way and is findable.

The standard

  • Org: [TEAM: Supabase org]; two projects per tool (<tool>-dev, <tool>-prod); region US East.

  • Database password generated into the vault (07.01). Never reused.

  • Project settings on creation: enable Point-in-time recovery on prod (Pro plan), set a connection pooler (transaction mode) for serverless use, enable network restrictions where possible.

  • Supabase CLI linked in the repo (supabase link); supabase/config.toml committed.

  • Types generated after every migration: npm run db:types → src/types/database.types.ts.

Procedure — new tool

  1. Dashboard → New project → name, region, password from vault.

  2. Record project ref, URL, anon key in the vault and .env.example.

  3. npx supabase init && npx supabase link --project-ref <ref>.

  4. Apply the template migrations (profiles, current_role()), then npm run db:types.

  5. Configure Auth per 08.01.

  6. Repeat for prod. Add both to 02.05.

Owner: [TEAM] · Last reviewed: 2026-09