Pushing Cells for NetBSD even further... cellmgr becoming a scriptable reconcilation engine with full lifecycle management including backup/restore, with cellui as the go-to TUI for midnight commander enthusiasts. And why stop there, when you could have a PAM authenticated web UI with feature-parity as well?
…and for those who wondered about the recurring MantisBT example in the screenshots - that is one of my end-to-end scenarios I use to test the practical viability of the Reconcile Engine, including things like volume management.
The scope is deliberately host-centric. It is not a cluster-wide deployment model like Kubernetes, but always framed around something like a sovereign home server, where I simply want to manage and operate my services in a clean and structured way.
For example, running a bug tracker with its database and reverse proxy - or something entirely different, like a Luanti game server for my son.
Some documentation has also started to emerge, because at this point it can no longer really be explained in a one-pager:
#netbsd #devops #modernretrocomputing #luanti #mantisbt #selfhosted #clt2026
What this page gives you This walkthrough is for admins who want one complete, realistic stack example from shipped manifests to running service. You will learn: how a multi-cell stack is modeled in manifests how dependencies (CELL_DEPENDS_ON) enforce rollout order how volume mounts model data ownership and persistence boundaries Shipped example location on NetBSD: /usr/share/examples/cellmgr/mantisbt Topology and dependency graph The MantisBT example has three cells and three volumes:
Matthias Petermann