supabase

When to Use

• Wiring Supabase into mobile, web, or server apps
• Adding or changing hosted Supabase env vars, auth redirects, or Edge Function calls
• Creating migration, link, deploy, or verification scripts around the Supabase CLI
• Reviewing whether a new Supabase env var or workflow is real product scope or accidental complexity

Critical Patterns

Keep the Public Env Contract Small

• Default public client contract to the minimum required values: project URL and anon key.
• Add extra public env vars only when runtime behavior truly needs them.
• Do not add a separate public Edge Functions base URL unless the project actually uses a non-default gateway or proxy.
• When possible, derive the functions URL from the project URL as <supabase-url>/functions/v1 instead of exposing another env var.

Separate Operator Secrets from App Config