infrastructure

one person, real production, no platform team. these posts are what that actually costs.

what does this blog cover about infrastructure?

the solo-founder stack first: what enterprise-grade actually means when it is just you and your wallet, and which parts of the expensive playbook are worth copying at one-person scale.

then the failures, which are the useful part. docker stack deploy silently dropping a command that docker compose config renders perfectly — along with three other swarm behaviours that fail without an error. and a production build that ran 46 hugo releases behind local for months: every deploy green, every config key i added silently ignored, and a fix that shipped broken for two days because the key that fixed it did not exist in the version doing the building.

the common thread is silence. none of these failed loudly. the compose key rendered, the build went green, the service came up — and the thing i asked for simply was not there. that is the failure mode worth writing about, because it is the one no alert catches.

• my production build was 46 releases behind and nothing failed — cloudflare pages built this site with hugo 0.118 while i developed on 0.164 — and the config key i added to fix a bug was silently ignored for two days
• docker stack deploy silently dropped my command (and 3 other swarm lies) — compose-spec keys that `docker compose config` renders but `docker stack deploy` quietly ignores — and how to catch them
• the solo founder's guide to enterprise-grade infrastructure on a budget — how to build production-ready infrastructure when it's just you and your wallet
• shipping a single self-contained go binary — embedded migrations and a self-writing config, so the service boots with zero external files

related

the deployment side is under go — shipping a single self-contained binary in particular.