Start Here
Start here for an overview of my homelab architecture and engineering blog series covering infrastructure, DNS, Docker, and monitoring.
Recommended Starting Point
If you're reviewing this as part of an application, start here:
This provides a full overview of the system, design decisions, and how the components fit together.
Detailed Breakdown
Each post focuses on a specific part of the system:
- Production-Style Homelab Architecture (Proxmox, Docker, DNS)
- DNS Architecture in a Homelab (Pi-hole and Unbound)
- Reverse Proxy Architecture (Nginx Proxy Manager and SSL)
- Docker Workload Design in a Homelab
- Monitoring a Homelab with Prometheus and Grafana
- Storage Architecture in a Homelab (RAID and Data Integrity)
- Network Design in a Homelab (Segmentation and Service Access)
- Backup Strategy in a Homelab (Data Protection Beyond RAID)
- Security and Access Control in a Homelab
About This Site
This site documents my transition from enterprise IT into infrastructure and cloud engineering.
The focus is on building and operating real systems rather than theoretical setups. Each post breaks down a component of my homelab and the decisions behind it.
The goal is to demonstrate practical engineering capability across networking, containerisation, monitoring, storage, and system design.
Start with the Architecture
If you're new, begin with the full system overview:
- Homelab Architecture: Proxmox, Docker, DNS and Monitoring
Core Components
The system is broken down into key areas:
- DNS (Pi-hole and Unbound)
- Reverse Proxy and ingress routing
- Container workloads (Docker)
- Monitoring and observability
- Storage and data management
Each component is explored in a dedicated post.
Approach
The focus is on:
- Designing systems with clear separation of concerns
- Understanding how components interact
- Diagnosing real issues rather than following guides
- Keeping solutions simple and maintainable
This is not a production environment, but it is designed with production thinking in mind.
What to Expect
Posts focus on:
- Real configurations and design decisions
- Problems encountered and how they were resolved
- Trade-offs between different approaches
- Practical insights from operating the system
The aim is to document the learning process in a structured and useful way.