L7 — Ship It Right
Track 2: Vibe-Coder Level-Up · B.U.I.L.D. letter: D (Document, Test & Deploy)
The last mile. "It works on localhost" is not shipped — it's a rehearsal. Here's how to put it in front of real people without it falling apart.
⚠️ The vibe trap
Deployment feels like a black box, so people either never ship, or they ship by uploading files and hoping. Then prod behaves differently from their laptop and they have no idea why. Demystifying this is the final step to "developer."
🌍 Environments: dev vs. prod
- Development is your machine — forgiving, full of debug tools.
- Production is the real world — real users, real data, no safety net.
- They differ in config, not code. The classic prod failure: an environment variable set locally but not in production. Your secrets and API keys must be configured in the host, not hardcoded.
🚀 Deploying
- Modern hosts (Vercel, Netlify, Render, etc.) deploy straight from your GitHub repo — push to deploy.
- Know your build step (what turns your source into what's served).
- Set your environment variables in the host's dashboard.
- Add a custom domain and confirm HTTPS is on (it should be automatic — verify it).
🩺 After you ship
- Monitoring: basic error tracking / uptime so you find out before your users do.
- Maintenance: dependency audits, updates, backups. Shipping isn't the end; it's the start of ownership.
- Rollback: know how to revert to the last good deploy before you need to. Most hosts make this one click — find that button today.
🛠️ Your mission
Deploy a project to a real host. Set its environment variables in production (not hardcoded). Confirm it works on the live URL over HTTPS — and locate your rollback button. Share the live link!
✅ You're done when…
- It's live on a real URL over HTTPS
- Env vars are set in production; no secrets in the code
- You know exactly how you'd roll back a bad deploy
➡️ Next: 🎓 The Capstone — bring an old app fully up to "Right." Build It Right, Or Don't Build It At All. 🏛️