1. What CI/CD actually does Learn what CI/CD means, what should happen before code gets merged or deployed, and how to set up a basic pipeline with GitHub Actions. 4 min
  2. Run your tests in CI Wire your test runner into GitHub Actions with one small workflow file, walk it line by line, and make the green check required so untested code can't reach main. 11 min
  3. Store and rotate secrets What counts as a secret, why it can never sit in your repo, and where it goes instead: a .env file locally, your host's dashboard in production, and a clear plan for the day a key leaks. 10 min
  4. Understand HTTPS and certificates What plain HTTP exposes on a shared network, what TLS and certificates actually promise, and the one HTTPS job your host still leaves to you. 9 min
  5. Check security before you ship A practical pre-ship pass for your first real app: secrets, user input, passwords, dependencies, HTTPS, and the rules client-side JavaScript can never enforce. 12 min
  6. Read logs and trace an error Where logs live once your app is deployed, how to follow a stack trace back to your own code, and what is worth writing to the log in the first place. 11 min
  7. Monitor your app and set useful alerts An outside uptime check, a health endpoint that actually touches the database, and alerts tuned so you still believe them. The minimum monitoring for a first real deployment. 11 min
  8. Track errors in production Why users never report crashes, and how an error tracker catches them anyway: a small SDK, source maps to decode minified stack traces, and triage by users affected instead of raw event count. 10 min
  9. Respond to a production incident An incident playbook for a team of one: confirm the outage is real, roll back before you debug, find the change that caused it, and write three sentences so the next one hurts less. 9 min