PROJECT NOTES / INFRASTRUCTURE
Proxmox Homelab
Infrastructure, made personal.
A self-hosted environment for exploring virtualization, repeatable deployments, and observability on repurposed hardware.
- Proxmox VE
- Docker
- Ansible
- Prometheus
- Grafana
- Nginx
THE CONTEXT
A closer look.
The problem
Running multiple self-hosted services creates a practical engineering problem: keeping deployments repeatable, access consistent, and failures visible.
What I built
I maintain a Proxmox VE environment with Home Assistant and Ubuntu Server virtual machines. Docker Compose defines services, Ansible provisions deployments, and monitoring separates infrastructure metrics from service availability.
HOW IT FITS TOGETHER
The architecture.
- 01
Proxmox VE hosts isolated virtual machines.
- 02
Ubuntu Server runs containerized services defined with Docker Compose.
- 03
Ansible automates service deployment; Nginx provides a consistent reverse-proxy layer.
- 04
Prometheus and Grafana expose infrastructure metrics; Uptime Kuma monitors availability.
ENGINEERING DETAILS
Decisions that matter.
Repeatable operations
Ansible copies service configuration and deploys Docker Compose stacks, reducing dependence on manual setup.
Observable systems
Node Exporter feeds Prometheus. Grafana visualizes host metrics, while Uptime Kuma handles availability checks and status-change alerts.
Deliberate boundaries
Internal DNS and a reverse proxy organize private service access. This portfolio presents a simplified diagram without addresses, credentials, or administrative endpoints.
Public homelab README and résumé. The illustration is a simplified architecture diagram, not a live dashboard.
UP NEXTAir Traffic Control Scheduler