This shelf is the public-facing corner of a much larger, French-language internal wiki that documents a personal homelab: a small Proxmox cluster, fully automated, that I use to learn, break, and fix real infrastructure on my own time.

Why a homelab, not just a cloud sandbox

I work in IT, in a regulated industry, where most of what I touch in production is locked behind change processes, segregation of duties, and (rightly) a lot of caution. That's necessary at work, but it also means I rarely get to see a full stack end-to-end, break it on purpose, and rebuild it from scratch to understand why it broke.

This homelab is that space. Three physical Proxmox nodes, a Kubernetes cluster, a firewall, an identity provider, a documentation wiki, a project tracker — all provisioned as code, all versioned, all disposable. Nothing here is "precious": if a VM dies, it gets rebuilt from Git, not restored from memory of how it was configured by hand three months ago.

Who this shelf is for

Peers: sysadmins, platform engineers, security folks, or anyone curious about running real infrastructure-as-code at home instead of clicking through a hypervisor UI. If you've ever wondered whether the discipline you apply at work (idempotent automation, documented incidents, least privilege) is worth applying to a homelab too, this is my answer: yes, and it's more fun than it sounds.

What this shelf shows — and what it doesn't

This is a curated selection from a much larger internal wiki, not the whole thing. You'll find:

• How the infrastructure is built and kept in sync with code (OpenTofu, Ansible, Git).
• How this very portal you're reading from was built, including the live 3D scene on its home page.
• A short tour of the AI agents I use to help operate this lab, and the guardrails around them.
• A couple of real incidents, told honestly, mistakes included.

You will not find: internal IP addresses, VM identifiers, hostnames beyond what's already visible in the public 3D scene, anything about my employer or its systems, or the compliance/hardening work I do professionally — that work is reproduced here in spirit (generic hardening exercises), never with real employer data, never connected to any real employer system.

If something looks intentionally vague, it's probably intentional. Enjoy the read.

I call each of these a chantier, French for a construction site: a bounded piece of work with a start, an end, and a write-up.