The gap between "it runs" and "it's in production"
You built something. It runs on your laptop. You git push, SSH into a server, run node server.js, see it respond on port 3000, and call it deployed. Then you close your terminal, and the app dies. Or it survives until the server reboots. Or it works, but a user's password is in your logs, the app is running as root, and the database is open to the entire internet. Every one of these is the same lesson: deploying isn't running your app on a different computer. It's running it in a way that survives reality.
Reality means crashes, reboots, traffic spikes, attackers scanning your ports, and a future you who needs to know why it broke at 3am. The good news: "production-ready" is not a vague vibe. It's a concrete, finite checklist. This article walks the whole thing, and by the end you'll have a mental model of the minimal real deployment plus the commands to build it.
Note: Who this is for: Beginners who can build an app but have never deployed one properly, or who deployed one and got burned. If you know how to SSH into a server and run a command, you have enough to follow. Examples use a Linux server and a Node app, but every concept maps to Python, Go, or anything else.
