Abandoned Deep depth Neutral outcome

Linux distro and self-hosting loop

Repeated cycles of distro hopping, Docker stack planning, and wanting a perfectly controlled setup that ended up creating more maintenance than leverage.

Technical category Operating Systems subcategory 5 cycles $420 spent ~220 hours time
research-heavy tag building tag optimizing tag recurring tag abandoned tag time-intensive tag solo tag

What triggered it

Started with reviving old hardware, then escalated into the belief that every service should be self-hosted.

Goal

Own the stack, learn Linux deeply, and reduce software subscription sprawl.

What I did

Ran Ubuntu, Fedora, Arch, and Proxmox phases, built media and note-serving experiments, and documented installs more than actual outcomes.

Summary notes

The terminal joy was real. The uptime anxiety and broken weekend after a casual change were also real.

Lessons learned

  • If the point is shipping a project, boring hosting often beats a beautiful homelab.
  • Backups are not real until restore is tested.

Mistakes and dead ends

  • Reinstalled instead of fixing incrementally.
  • Turned infrastructure learning into a substitute for actually publishing the site.

Related focuses

Same neighborhood

Homelab and hosting rebuild

A corrective cycle after overcomplicating hosting. Ended with a healthier respect for cheap shared hosting, static-first builds, and...

AI workflow lab

Less about hype and more about turning AI into an actual workbench for writing, synthesis, product architecture, and...

Related tools

What stayed useful

Sublime Text

Fast, lightweight, and still one of the cleanest editors for quick code edits, config changes, and low-friction writing or scripting work.

Lessons and offers

Carry something forward