Backups and the security checklist
Back up Adjoa's Kitchen (the database's structure in Git, and its data exported to a safe place outside the project), check the backup really opens, then create SECURITY-CHECKLIST.md in your project, go through every line with proof, and keep a blank copy for every site you launch from now on.
Why this matters
Every lesson in this module has protected Adjoa's data from strangers. This one protects it from accidents. A wrong click in the Table Editor. A migration that drops the wrong column. A problem with an account. One bad afternoon, and a month of orders, customers and phone numbers is gone.
The answer is a backup: a copy of the data, kept somewhere else, that you've checked you can actually open. Supabase's free plan doesn't give you backups you can download (paid plans take daily ones), so you'll make your own. It takes ten minutes.
Then you'll do the thing professionals do and beginners skip: write it all down. Everything you checked in this module becomes one file, SECURITY-CHECKLIST.md, kept in the project. Before any site goes live (starting with your first client site in Module 11), you work through it line by line, with proof. Not from memory, not "I think I did that". That file is the difference between "I'm fairly sure it's secure" and "here's what I checked, and when".
In the full lesson
- The idea in plain English
- Do it
- Check it worked
- Quick check
- What you can do now
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.