Shipping It

Most of what stops people shipping is not code. It is a domain that will not resolve, a key committed by accident, a bill that arrives three weeks later, and a backup nobody has ever restored. This course covers the boring machinery between "it works on my laptop" and "strangers are using it" — servers, DNS, HTTP, secrets, deploys, logs, cost, abuse and recovery — with real numbers and real failure modes. You need to have built something small already. You do not need to have deployed anything.

1. 1What a server actually is7 minA server is just a process holding a port open; the cloud only changes who owns the machine.
2. 2Why your site is not loading8 minNothing propagates; DNS answers are cached for their TTL, so lower the TTL before you change anything.
3. 3What a status code is telling you7 minThe first digit says who has to fix it; a status code that lies makes every layer above you lie too.
4. 4The key you must not commit8 minA leaked key is only fixed by rotating it; scrubbing git history does not un-leak anything.
5. 5Deploying for nearly nothing8 minBoth versions run during a deploy, so schema changes take three deploys, not one.
6. 6Reading logs at 2am7 minGive every request an ID and log it everywhere; that one habit turns guessing into searching.
7. 7The bill, and the traffic that runs it up9 minAlerts tell you the money is gone; only caps, limits and caching stop it leaving.
8. 8The restore you have never tested8 minAn untested backup is a guess; the drill is the only thing that turns it into a plan.