006 / planned
compose-sketch
A compose layout for the home lab where each service can fail alone.
What
A planned layout, not a running platform. One compose file per service. Shared names for the network and the volumes I mean to keep. Nothing else shared.
Why
A single stack that boots the house is easy to write and annoying to reason about. I want a service to be stoppable without a speech about the others.
Architecture
Each file declares its own service, the ports it is allowed to publish, and the mount that holds its data. A network is created on purpose and named. The internal proxy is just another file, not a privilege baked into the host.
Discoveries
None yet. The note exists so the plan is a file, not a memory. The first thing to get wrong, on purpose, is a port published to the host that nobody asked for.