Mild irony worth admitting: the log of a self-hosted infrastructure project is a static site with no infrastructure at all.

That is deliberate, and the reason is the thing this site is about.

For two years the notes lived in a self-hosted wiki. It was good software. It also needed a container, a database, a reverse proxy entry, a certificate, a backup job that understood the database, and an upgrade every few weeks that occasionally wanted the database migrated. The documentation of the homelab had become a component of the homelab, with its own failure modes.

Then the disk problem happened, and the notes about disk problems were on the array with the disk problem.

Now it is HTML. The pages are written on a phone, generated into a folder, and pushed over SFTP to a server that does nothing except serve files. The backup is a directory of text. If the machine under the stairs is off, on fire, or halfway through a resilver, this still loads, because it is not there.

There is a broader point about the homelab hobby here. The instinct is to self-host everything, and most of the time that instinct is right — you learn more, you own more, you depend on fewer people. But every service you run is a thing that can be down at the worst possible moment, and the worst possible moment for your documentation is precisely when everything else is broken.

So: the array holds the data. The cupboard holds the machine. The notes about both live somewhere boring, in the dumbest possible format, on hosting I could replace in an afternoon.

That is not a compromise. It is the correct architecture for the job.