🖥️ Proxmox Home Lab
The host everything else runs on. Proxmox VE, running the VMs and containers behind every other project here — snapshotted and backed up so I can break things safely.
Overview
I wanted real hardware I could break and rebuild, not a cloud sandbox that resets when the free tier runs out. So I built my own. The host now runs everything from a Jellyfin container to an OPNsense firewall VM.
It's the base layer for every other project here. That also makes it where I learned the operations discipline: snapshot before risky changes, schedule backups, rebuild broken services instead of guessing at fixes.
Architecture
Technologies Used
- Proxmox VE
- Ubuntu Server
- Docker
- Linux
- Git & GitHub
- PowerShell
- TCP/IP Networking
Highlights
- Built and manage a Proxmox virtualization environment.
- Deploy Linux virtual machines for testing and development.
- Host multiple Docker services.
- Practice networking and storage configuration.
- Document infrastructure using GitHub.
- Add new services and rebuild broken ones as the lab grows.
Challenges
- Learning Linux permissions and file ownership.
- Understanding Docker networking.
- Configuring shared storage.
- Troubleshooting container deployments.
- Managing virtual networking inside Proxmox.
What I Learned
The habits mattered more than the technology. Snapshot before you change something. Back up before you trust it. Rebuild from a known-good state instead of troubleshooting blind — discipline that's invisible until the day it saves you.