🔄 GitOps Infrastructure

Repository: github.com/jhathcock-sys/Dockers

Project Overview

Infrastructure as Code for my homelab environment. All Docker Compose configurations are version-controlled in Git, enabling reproducible deployments, change tracking, and easy rollbacks.

This is a stepping stone toward full Kubernetes orchestration, building GitOps practices while working with Docker Compose.

📁 Repository Structure

homelab-ops/
├── proxmox/                    # ProxMoxBox (192.168.1.4) stacks
│   ├── dockhand/               # Docker management UI
│   ├── homepage/               # Dashboard + config files
│   │   └── config/             # services.yaml, widgets.yaml, etc.
│   ├── homelab-tools/          # Homebox asset inventory
│   ├── minecraft/              # PaperMC + Geyser/Floodgate
│   ├── monitoring/             # Full observability stack
│   │   ├── alertmanager/       # Alert routing config (Discord)
│   │   ├── prometheus/         # Scrape configs + alert rules
│   │   ├── loki/               # Log aggregation config
│   │   ├── promtail/           # Log collector config
│   │   └── grafana/            # Dashboard provisioning
│   ├── nginx-proxy-manager/    # Reverse proxy
│   └── uptime-kuma/            # Service health monitoring
│
└── pi5/                        # Raspberry Pi 5 stacks (via Hawser)
    ├── infra/                  # Pi-hole + Tailscale
    ├── mealie/                 # Recipe management
    └── nebula-sync/            # Pi-hole sync

🚀 Deployment Workflow

Local Stacks (ProxMoxBox)

# 1. Edit compose files locally
vim proxmox/homepage/docker-compose.yaml

# 2. Commit and push
git add . && git commit -m "Update homepage config"
git push

# 3. On server: pull and deploy
cd /opt/homepage
git pull
docker compose up -d

Remote Stacks (Pi5 via Hawser)

Pi5 stacks are managed remotely through Dockhand’s Hawser agent:

• Compose files live on ProxMoxBox at /opt/pi5-stacks/
• Hawser executes commands on the Pi5 Docker daemon
• No SSH required for routine deployments

🗺️ Path Mapping

🔧 Stack Management with Dockhand

Dockhand provides a web UI for Docker management:

• Stack Import: Adopt existing containers by pointing to compose files
• Remote Management: Hawser agent enables control of remote Docker hosts
• Compose Editing: Edit and redeploy stacks from the UI

Key Configuration

services:
  dockhand:
    image: fnsys/dockhand:latest
    environment:
      - HOST_DATA_DIR=/opt          # Path resolution for stacks
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /opt:/opt                   # Access to all compose files

🔐 Secrets Management

Sensitive values are kept out of Git using .env files:

# Template provided in repo
cp .env.example .env

# Generate encryption keys
openssl rand -hex 32

Pattern:

• .env.example → Committed (templates with placeholders)
• .env → Gitignored (actual secrets)

📊 Current Stacks

ProxMoxBox Services

Pi5 Services (via Hawser)

🖥️ Non-Docker Services

Some infrastructure runs on dedicated VMs outside the GitOps workflow:

These are managed separately but integrate with the Docker-based services (e.g., Wazuh agents on Docker hosts report to the SIEM).

📋 Future Plans

• Implement CI/CD pipeline for automated deployments
• Add pre-commit hooks for YAML linting
• Migrate to Kubernetes with ArgoCD
• Set up Renovate for automated image updates