Shipping to Production
You have been building. The app works on your machine, the demo wowed a friend, and the itch to put it out into the world is real. This is the moment a lot of solo builders stall — not because the code is broken, but because "going live" feels like a different discipline with its own dark arts: ( Name System, the internet's address book that turns a name like yourdomain.com into the number a server lives at), servers, secrets, payment webhooks. Good news: this is exactly the kind of mechanical, well-documented work that AI is best at. Your job is to direct. Their job is to type the commands.
But "direct" is the load-bearing word. The theme of this whole book is understand what you ship. You do not need to memorize the flags, but you do need to know what each step is for — what a protects you from, why a must never hit your repo, what a spend cap is caging. When you understand the shape of the thing, you can tell when the AI's confident answer is quietly wrong, and you can recover when the first explodes. The builders who get burned at launch are almost always the ones who pasted commands they could not read.
This chapter walks the whole last mile, from a working local app to a real (Uniform Resource Locator, the web address people type into a browser) people can pay you through.