The database: services and bookings

About 90 minutesYou need: your project open in Cursor, the Supabase dashboard, your password manager, and adjoas-kitchen (you'll copy two proven files from it)
This video is in the full courseGet the course to watch every video and read every lesson in full. GHS 399, paid once.Get the course · GHS 399
Video · 24:59
Goal

Create a new Supabase project for your client site, connect it to Cursor through the MCP, create the services and bookings tables by prompt, lock them with grants and RLS, make the site read its services from the database, and prove with an eight-line stranger test that a visitor can't read, change or fake anything.

Why this matters

Everything so far is a brochure. From this lesson on, the site starts doing the work the owner will pay for: keeping a list of booking requests that nobody can read except them.

You've done every step of this in Module 7 and Module 10, for Adjoa's dishes and orders. You'll do them again here, faster, and in the same order, because the order is what keeps you safe:

  1. Create the tables, with RLS switched on from the start.
  2. Add the starting data.
  3. Grant exactly what the public needs, and write the policies.
  4. Prove it from the outside, before any page uses it.

Go slowly. Read every SQL statement before you approve it. This is the lesson where a careless "Run" would leave a client's customers' phone numbers open to the internet.

In the full lesson

  1. The idea in plain English
  2. Do it
  3. Check it worked
  4. Understand what AI wrote
  5. Quick check
  6. What you can do now
Stage 2 · Make it workYou’ve seen the why. The how is in the course.

The step-by-step, the prompt to copy, the video and the check-it-worked list, for every lesson in all 15 modules. GHS 399 ($40), paid once by mobile money or card, yours to keep.

Get the course · GHS 399See what’s inside
Already have the course? Open the full lesson