Supabase
Create a Supabase project and connect the backend in OpenQuok.
Connect your agent today
Draft from chat, review in your calendar, and publish only what you approve.
Overview
Supabase configuration for this project is split between:
- Dashboard settings (database, auth, integrations such as cron)
- Backend environment variables (Supabase URL + keys)
API keys
OpenQuok uses Supabase’s new API key format only — the legacy JWT-based anon / service_role keys are not accepted. Background:
| Role | Variable | Format |
|---|---|---|
| Public / client-side | PUBLIC_SUPABASE_PUBLISHABLE_KEY | sb_publishable_… |
| Server-side (elevated) | SUPABASE_SECRET_KEY | sb_secret_… |
Warning
Note
anon / service_role JWT keys, open Settings → API Keys in the Dashboard and create a Publishable key plus one or more Secret keys, then update your env vars to the new names.Steps
Create a Supabase project
Create a project in the Supabase Dashboard and keep your database password.
Collect API keys (production / hosted Supabase)
In the dashboard, open Settings → API Keys:
- Copy the Publishable key (starts with
sb_publishable_). - Create at least one Secret key (starts with
sb_secret_) for the backend.
…and set them in backend/.env.production.local:
PUBLIC_SUPABASE_URL=https://your-project-ref.supabase.co
PUBLIC_SUPABASE_PUBLISHABLE_KEY=sb_publishable_...
SUPABASE_SECRET_KEY=sb_secret_...Collect API keys (local development)
Local supabase start emits the new key format from Supabase CLI 2.45+. Pull them with:
cd backend
supabase status -o env…and set them in backend/.env.development.local:
PUBLIC_SUPABASE_URL=http://127.0.0.1:54321
PUBLIC_SUPABASE_PUBLISHABLE_KEY=sb_publishable_...
SUPABASE_SECRET_KEY=sb_secret_...If supabase status still prints anon key / service_role key instead of Publishable key / Secret key, upgrade the CLI.
Configure auth settings (as needed)
If you use email confirmation or third-party providers, configure them in the Supabase Dashboard under Auth settings.
Cron on Supabase Cloud (pg_cron)
Some modules use a cron job (via pg_cron) on Supabase Cloud.
Warning
If you need to enable it manually, Supabase’s docs show the required SQL and grants.