Database Management (Supabase)

1. Core Workflow

• •Environment: We use Supabase (PostgreSQL + Auth).
• •Local Config: supabase/config.toml manages local settings.
• •Env Vars: Ensure .env.local is populated with valid Supabase credentials.

2. Key Commands

• •Push Migrations: npm run db:push
  • •This pushes schema changes to the remote Supabase instance.
  • •It also pushes the local configuration.
• •Link Database: npm run db:link
  • •Links the local development environment to the remote Supabase project.
• •Generate Types: npm run db:types
  • •Generates TypeScript definitions from the database schema. Run this after every schema change.
• •Deploy: npm run deploy:supabase
  • •Deploys migrations and config (often used in CI/CD).

3. Schema Management

• •Migrations: SQL migrations are located in libs/db/src (or supabase/migrations depending on the exact setup - check supabase/config.toml workdir).
• •Validation: Always verify schema changes locally before pushing to production.

4. Troubleshooting

• •CSP/Connection Issues: If the build fails to connect to Supabase, check the Content Security Policy (CSP) headers in next.config.js or middleware.ts.
• •Url Sync: Ensure NEXT_PUBLIC_URL matches your site_url in Supabase config to prevent redirect issues with auth.