V0.1 / START HERE
My homelab,
explained piece by piece.
I run a personal infrastructure environment to host useful applications and practise systems engineering. This site explains what is in it, how it is built and how I operate it.
The foundation is a three-node Proxmox cluster, a separate Linux host and a QNAP NAS. Linux environments run Docker Compose stacks; shared services provide naming, HTTPS, databases, automation, monitoring and backups.
A SIMPLE READING ORDER
New here? Start with these three pages.
What is here?
The hardware and the virtualisation foundation.
Read the page →02 / START HERE ↗How is it connected?
The relationship between compute, applications and data.
Read the page →03 / START HERE ↗What does each service do?
The actual services, their dependencies and operation.
Read the page →One lab. Three perspectives.
A map of responsibilities. Private placement and network routes are omitted; links do not imply complete HA coverage.
- STEP 01Resolve the service name
- STEP 02Reach the HTTPS entry
- STEP 03Match the Traefik route
- STEP 04Call the application
Databases, document files and background workers have their own responsibilities. Follow those dependencies in each service guide.
Configure & deliver
Git → reviewed automation → running environment
Ansible · Semaphore · delivery workflows →These are complementary practices, each with its own checks and dependencies.
SERVICES, FOUNDATIONS & EXPERIMENTS
Find a service by what it does.
Platform & networking
Data & recovery
Automation & operations
Monitoring & logs
Home automation
HOW I OPERATE IT
Building the service is only the beginning.
Deploy & change
Git, a repeatable server baseline, Semaphore tasks and Compose delivery workflows. See the actual sequence and its checks.
How I deploy →Observe & investigate
Zabbix detects symptoms, Elastic provides event context, and a secondary Kuma view checks selected reachability.
Monitoring & logs →Protect & restore
VM backups are one layer. Databases, files, configuration and secure dependencies have to come back together.
Backups & recovery →How to read this V0.1
This is the public documentation of a real lab, with selected runtime checks and operational records reviewed on 29 October 2026. It is not a live inventory or status board. Service pages state known limitations; examples and diagrams omit private identifiers. The roadmap separates implemented work from future experiments.