ON STANDING UP A BOX

You rack the machine, you give it a name, you wait for the cursor.

Debian comes up quiet. SSH with a key and IdentitiesOnly, because agent soup is how you log into the wrong host and spend twenty minutes wondering why the disk looks like someone else’s. Docker after that. A reverse proxy in a container listening like a nightwatchman on 80 and 443. The blog sits on 8000 and pretends it has always been there.

Standing up a box is not a ceremony. It is a sequence you can hold in your head:

1. Image it. Name it. Put it on a network you can explain.
2. Patch it before you love it.
3. One service, one compose file, one restart policy that actually restarts.
4. Logs you can docker compose logs at 2am without opening a dashboard.

I do not want a control plane for a weblog. I want a process bound to a port, a volume that is just files, and the knowledge that if the tube goes dark I can bring it back with --build -d and a cup of something that was coffee an hour ago.

This page is the test pattern. Green on black. If you can read it, the tube is warm.