Ansible
Dynamic Proxmox inventory, three idempotent roles, and the playbooks that provision and maintain the fleet.
Toolsera Infrastructure
One place for everything that runs the homelab — how it is provisioned, how it is deployed, and how to operate it without re-deriving the details each time.
What lives here
Section titled “What lives here”Docker stacks
Every Compose stack in the repo, with services, images and published ports generated straight from the compose files.
Packages
Custom .deb packages built with dpkg-deb or FPM and published to the
internal Nexus APT repository.
Operations
Verified host access notes, connection gotchas, and the rules for changing things on a live host safely.
The shape of the system
Section titled “The shape of the system”The homelab runs on Proxmox. Guests are discovered dynamically rather than listed by hand, configured by Ansible, and run their workloads as Docker Compose stacks fronted by Traefik. Secrets never live in the repo — they are injected at container start from Bitwarden Secrets Manager. Custom tooling ships as Debian packages through an internal Nexus APT repository.
Architecture How provisioning, routing, secrets and package distribution fit together.
Conventions Internal domains, naming rules, formatting and the pre-commit hooks.
How this site stays accurate
Section titled “How this site stays accurate”Most pages here are not written for the site. They are the repo’s own README files,
copied into the hub at build time and rewritten so their links resolve. The README
stays canonical in its directory, so browsing the repo on GitHub still works and the
hub cannot drift from it.
The stack catalog goes further: it is generated by parsing the
compose files themselves — including their include: directives — so adding a stack
adds a catalog entry with no documentation edit at all.