It’s been a few months since I last wrote about the self-hosted stack running on my VPS — Fedora Server, MicroShift, everything deployed through Flux. The cluster has been quietly doing its job, which is the entire point, but a fair amount has changed underneath. This is the round-up: what I optimised, the package repository I ended up building myself, and why I threw away the documentation page and wrote it again from scratch.
[Read More]One Month of MicroShift: A Homelab Retrospective
One month in. The migration from Gentoo + Docker to Fedora Server 43 + MicroShift is complete and everything is running in production: mail stack, Nextcloud, Vaultwarden, Paperless, Collabora Online, monitoring, and this website — all on a single VPS, orchestrated by Kubernetes, managed by GitOps. So far, so good.
But let me be honest about the complexity. The full documentation runs to eight major sections covering base system, storage, firewall, WireGuard, MicroShift, GitOps, TLS, and eight services with their operational scripts. Behind that documentation are 368 commits across two repositories in four weeks — 232 in the GitOps manifests repo alone, 136 in the runbook. That’s not a “deploy and forget” setup. Every one of those commits represents something that had to be figured out, fixed, or explicitly decided.
[Read More]