infrastructure-stack

What problem does it solve?

Infrastructure-stack removes the guesswork and recurring breakages of self-hosted deployments by standardizing how Docker Compose stacks are networked, exposed, permissioned, health-checked, and integrated with the user’s host-mode Caddy reverse-proxy pattern.

Core Features & Use Cases

• Compose-first stack conventions: One service per stack with deterministic bridge networking, static IPs, and clear separation of public vs internal dependencies.
• Caddy integration without ports on backends: Uses expose for backend services while keeping external access centralized in a separate Caddy stack pinned to static IP routing.
• Operational hardening: Enforces image tag pinning, LinuxServer-style PUID/PGID/UMASK defaults (or explicit user:), per-service healthchecks, resource limits, and safe bind-mount storage layout.
• Migration path guidance: Provides decision points for when to stay on Compose, graduate to k3s, or move to Proxmox VM patterns (including multi-host and secret-management scaling triggers).

Quick Start

Use infrastructure-stack as your template when creating a new docker-compose.yml stack by selecting an unused 172.19.X.0/24 subnet, assigning static container IPs, configuring backend expose (not published ports), and then adding the matching Caddyfile virtual host pointing at the same static IP and port.