Supabase

Recommended: project URL and access token

1. Click Server › Backend › Set up Supabase.
2. In Supabase, open the project, choose Connect and copy the project URL, like https://abcdefghijklmnopqrst.supabase.co.
3. Create a token under your avatar › Account preferences › Access Tokens, not in the project's API settings. It starts with sbp_.
4. Keep Project URL + access token selected, paste both and save.

Supabase shows the token once. A scoped token needs read-write on Database, Edge Functions and Edge Function Secrets. It reaches every project in your account, so make one just for FluxNative, with an expiry.

Keys only

Rather not share an account token? Choose Keys only and paste the publishable key (sb_publishable_…) and a secret key (sb_secret_…) from Project Settings › API Keys. Legacy anon and service_role keys work too. The assistant can then manage users and files, but cannot run SQL or deploy functions: create tables and policies yourself in the SQL editor.

Then ask

Supabase is connected. Add email sign-in. Store each member's bookings in a
table with the class, the time, and the member. Members can only read and
cancel their own bookings.

For a business that takes bookings, say whether customers book as guests (a name and a phone number) or sign in, and ask for the sample data's services as starting rows. Bookings show in the Table Editor. See Moving from sample data.

Good to know

• The publishable key ships in the app; row-level security protects the data. The secret key stays on the server, and the form refuses it in the publishable box.
• Keys an Edge Function needs, such as an email provider's, go under API keys and secrets.
• Supabase's Free plan needs no card and allows two active projects, each with a 500 MB database, 1 GB of file storage and 50,000 monthly active users. It pauses a project after 7 days without activity: the data is kept, and the owner restores it from the Supabase dashboard. Pro, from $25 a month, keeps it running.

Related

API keys and secrets · Server