Homelab Portfolio¶
This lab practices reliable infrastructure operations as a small production environment. It is documented from my Homelab Infrastructure & Operations Manual, version 1.0 (October 2026).
Sanitized document
Addresses are shown as 192.168.X.X, domains as service.example.net, and
secrets only as environment-variable references. Commands and snippets are
representative; values must be validated against the live environment
before use.
At a glance¶
| Item | Value |
|---|---|
| Physical hosts | 3 (two Proxmox VE nodes, one Unraid storage and application server) |
| Public inbound ports | 0 (remote access through a Tailscale WireGuard mesh) |
| DNS instances | 2 (redundant AdGuard Home, synchronized configuration) |
| Manual version | 1.0, October 2026 |
Design principle: prefer the lightest suitable workload type, keep management access private, validate service health beyond process state, and document a recovery path before changing things.
What the lab demonstrates¶
- Proxmox VE with LXC containers, and VMs where appropriate.
- Docker on storage-backed Unraid.
- Split DNS with consistent service names.
- Caddy reverse proxy with automated wildcard certificates.
- Tailscale (WireGuard) remote access with no internet-exposed service ports.
- Prometheus and Grafana monitoring.
- Custom Bash health checks with retry limits, recovery and alerts.
- Documented maintenance, backup, rollback and Terraform practice workflows.
Skills¶
Proxmox VE, LXC, Docker, Unraid, Linux, Bash, DNS, HTTPS/TLS, Caddy, Tailscale, WireGuard, Prometheus, Grafana, Terraform, cloud-init, troubleshooting and documentation.
Where to start¶
- Architecture: topology, platform inventory, placement rules, secure access and security controls.
- Services: AdGuard Home, Caddy, Tailscale, Prometheus and Grafana.
- Automation: self-healing health checks and Terraform practice.
- Operations: maintenance, backup, rollback and checklists.
- Troubleshooting: incident-response checklist and a mock incident log template.