Home lab · Draft ·
The home server behind all this
One quiet box in the house runs the games, this log and the status page.
Everything on Fiddleden runs on one small server in the house. No cloud bill, no ads, and the games keep working as long as the internet does.
The pieces
- Containers for everything. Each game, the front door and the status page run in their own Docker container. Each one gets only the permissions it needs, and its files are read-only.
- A front door. One small web server answers for fiddleden.com. It serves this log as plain files, hands game traffic to the right container, and adds the security headers to every response.
- A tunnel, not open ports. The house doesn’t accept connections from the internet. The server dials out to Cloudflare, and visitors reach it through that tunnel.
- A status page. A watcher checks each public service every minute. The dot in the footer is green when they all answer.
Shipping changes
The code lives in a private repository. Pushing a change runs the tests against throwaway copies of the games, snapshots the real databases, and only then swaps in the new containers. If something goes wrong, the previous images are tagged and one command puts them back.
This is a draft. More detail as the setup settles.