← Atlas

homelab · build log 001

The Monstrosity

A bolted-together, beautifully chaotic homelab. Three machines, ten drives, one private line — routed by a proxy that thinks for itself, fronted by a door with no holes punched in the firewall.

pre-ignition — build log below
// build log 001 · node fedora-01 Read the build log → Five phases · troubleshooting · ignition sequence
status: pre-ignitionclass: tinkerer’s utility
The Monstrosity — a look inside, on desktop and phone
inside the app · desktop and phone

why this exists

Opened, understood, grown

the idea

Not a rented cloud tier and not a black box you trust and forget — a stack built to be opened, understood, and grown. Storage is one organ among many. It's also where the rest of the atlas is meant to live: the log names Weaver and muse among the first tenants.

the plan
the rule

Isolate the layer before you debug it. Drive, share, container, proxy, tunnel — each keeps its own logs, and the log's troubleshooting section starts from dmesg and ends at cloudflared without ever guessing across layers.

FedoraSambaDocker ComposeTraefikCloudflare TunnelNextCloud
honest scope

Pre-ignition: this is the plan and the troubleshooting rules, not a running cluster — the ignition checklist is still unticked, and the drive-labelling scheme is an open thread. Cloudflare sits in the middle of external traffic; the log names that trade-off out loud and leaves it to be revisited.