The secrets rules
Know exactly which values are secrets, the four places a secret must never go, how to ask for help without leaking one, and the five steps to take, straight away, if a key ever leaks.
Why this matters
From the next module on, you'll hold real keys. A database key that can read Adjoa's customers' phone numbers. Later, an email key that can send messages in a business's name. One day, a client's keys too.
Leaked keys are one of the most common ways small websites get into trouble, and it almost never happens through clever hacking. It happens through ordinary moments: a screenshot posted in a group to ask for help, a key pasted into an AI chat "just to check it", a file pushed to GitHub at midnight. Automated programs scan GitHub for keys around the clock and can find a fresh one within minutes.
The good news: the rules are short, and the fix for a leak is simple, as long as you do it immediately. This lesson gives you both. Learn them now, while you have nothing to lose, so they're habits by the time you do.
In the full lesson
- The idea in plain English
- Try 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.