Modular, reproducible Docker Compose infrastructure for self-hosted environments.

Designed to scale from a small setup to a fully structured homelab with clean separation between services, templates, and infrastructure layers.

This repository provides a structured approach to managing self-hosted services using Docker Compose.

Instead of maintaining large monolithic compose files, services are:

• isolated
• reusable
• environment-driven
• easy to extend

• Modularity first — one service per stack
• No hardcoded values — everything configurable via environment variables
• Separation of concerns — infrastructure, services, and templates are clearly split
• Reproducibility — consistent deployments across environments
• Scalability — designed to grow with the homelab

homelab-compose-stack/
├── stacks/        # actual service deployments
├── templates/     # reusable service/stack templates
├── networks/      # shared network definitions
├── scripts/       # helper utilities
└── .env           # centralized configuration

• Rapid deployment of new services
• Consistent configuration across stacks
• Clean separation between configuration and logic
• Easy migration between hosts or environments

This stack is designed to support common homelab services such as:

• Media management (Jellyfin, Radarr, Sonarr)
• Monitoring (Uptime Kuma, Grafana)
• Infrastructure tools (Portainer, reverse proxies)
• Automation pipelines

• Docker / Docker Compose
• Linux-based environments
• Environment-driven configuration

Actively evolving — focused on building a clean, scalable foundation for long-term homelab management.

Infrastructure should be predictable, reproducible, and easy to extend.

This repository is primarily for personal infrastructure, but ideas, improvements, and discussions are always welcome.