How to find your Supabase project URL and API keys
Find optional Supabase storage values for BaseBuddy mapped media and file fields.
BaseBuddy requires a Postgres database URL. Supabase project URL and API keys are optional. Add them only if you want images or files in BaseBuddy.
BaseBuddy login, users, projects, permissions, invites, mappings, and sidebar layout live in app data, not in Supabase-hosted auth. Supabase/Postgres app-data mode uses BaseBuddy-owned basebuddy tables only when you select that backend.
Values you may need
| Supabase value | BaseBuddy env value | Use |
|---|---|---|
| Project URL | BASEBUDDY_SUPABASE_URL | Connect to Supabase Storage buckets |
| Publishable key | BASEBUDDY_SUPABASE_PUBLISHABLE_KEY | Browser-safe Supabase client access where needed |
| Server key | BASEBUDDY_SUPABASE_SECRET_KEY | Server-side storage work |
Keep the server key private.
Find the values in Supabase
- Open the Supabase project that stores your content buckets.
- Go to Project Settings.
- Open API or Data API.
- Copy the project URL.
- Copy the publishable key.
- Copy the server-side key.
Dashboard labels can vary. Supabase may call the publishable key an anon key in older projects.
Save values during setup
Save these values in .env or in your production host env:
shBASEBUDDY_SUPABASE_URL=https://your-project-ref.supabase.co
BASEBUDDY_SUPABASE_PUBLISHABLE_KEY=your-publishable-key
BASEBUDDY_SUPABASE_SECRET_KEY=your-server-keyThese values are not saved in app data.
Rotate exposed keys
If a server key was committed, posted, or shown in a screenshot, rotate it in Supabase and update BaseBuddy setup with the new value.
For database passwords, use How to find or reset your Supabase database password.