Docker Compose stacks for docwho homelab
  • Shell 83.3%
  • Python 16.7%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2026-11-21 22:05:01 -08:00
.forgejo/workflows Update docker:29-cli Docker digest to 34507eb 2026-11-17 06:07:33 +00:00
bootstrap bootstrap: let short image names resolve to Docker Hub on forbin 2026-11-15 06:59:36 +00:00
docs Health skills: follow the arr-mcp 2.x, grafana-mcp 2.3 and kubernetes-mcp 0.1 upgrades 2026-11-21 10:16:19 +00:00
hermes/skills Health skills: follow the arr-mcp 2.x, grafana-mcp 2.3 and kubernetes-mcp 0.1 upgrades 2026-11-21 10:16:19 +00:00
hosts Update ghcr.io/bardesss/arr-mcp Docker tag to v2.3.2 2026-11-22 06:04:43 +00:00
scripts deploy-forbin: put Hermes skills in their category directory 2026-11-14 11:28:50 -08:00
turnstone/skills Health skills: follow the arr-mcp 2.x, grafana-mcp 2.3 and kubernetes-mcp 0.1 upgrades 2026-11-21 10:16:19 +00:00
.gitignore Alloy on every Compose host; kubernetes-mcp and grafana-mcp on farnsworth 2026-10-04 07:01:46 +00:00
LICENSE Initial commit 2026-09-28 01:28:43 -07:00
README.md Docs: point at talos-gitops' docs/ for homelab-maint and kubernetes-mcp 2026-11-14 13:21:25 -08:00
renovate.json Add forbin: Podman Quadlets for gufo and Alloy, deployed like the other hosts 2026-11-13 21:14:53 -08:00

homelab-compose

Docker Compose stacks for farnsworth and the Raspberry Pis, Podman Quadlet units and Hermes skills for forbin. Renovate keeps image versions current; Forgejo Actions deploys on merge.

repo host (hosts/<host>/) IP hardware runs
farnsworth 192.168.1.252 Core i5-13600K Traefik, Forgejo + runner, Immich, MCP servers, Turnstone, Open WebUI
utilitybelt-1 192.168.1.218 Raspberry Pi 4 (USB SSD) Pi-hole, Garage, Uptime Kuma
utilitybelt-2 192.168.1.219 Raspberry Pi 4 (USB SSD) Pi-hole, Garage
utilitybelt-3 192.168.1.224 Raspberry Pi 5 (NVMe) Garage, MeshMonitor
forbin 192.168.1.223 Framework Desktop (Ryzen AI Max, gfx1151) Podman, not Docker: gufo, Lemonade, Hermes

Every host also runs Alloy. Everything in git (paths, host labels, alerts, monitors) uses the repo name and the IP, never the OS hostname.

Layout

hosts/<host>/PLATFORM                        linux/amd64 | linux/arm64 (validate checks images exist for it)
hosts/<host>/<abs path>/docker-compose.yml   deploys to <abs path> on <host>
hosts/forbin/...                             Quadlet units and config, same mirroring
hermes/skills/, turnstone/skills/            health-check skills, one directory per agent
bootstrap/                                   one-time host setup scripts (not deployed)
scripts/                                     validate, deploy, cache, known_hosts

To add a stack, create its directory; nothing else to register. Only tracked files are copied to the host. .env, secrets and data stay host-only (.gitignore); ship a .env.example next to any compose file that uses a .env.

How a change ships

  1. Renovate (run from talos-gitops' workflow) opens PRs bumping image tags, pinned by digest.
  2. validate renders every stack and checks every image exists for its host's architecture.
  3. Patch, minor and digest updates automerge. Majors, Immich, Garage, Forgejo minors, Turnstone and gufo-runtime wait for you.
  4. On merge, deploy-<host> runs on farnsworth's runner and updates only the stacks whose files changed. Hermes then checks the host and reports.

Details, secrets and failure handling: docs/deploys.md.

Docs

doc covers
deploys.md deploy flow, CI secrets, runner capacity, lookup cache, Traefik config
pi-hosts.md setting up or renaming a Pi; Docker image store, log cap, reboot watchdog
forbin.md Quadlets, forbin deploys, the apply script, gufo, Alloy on forbin
monitoring.md Alloy on every host, what it ships and where
mcp-servers.md talos, kubernetes, grafana, arr and Home Assistant MCP servers; setup steps
agents.md Turnstone, Open WebUI, Hermes; skills and how they deploy
garage.md the three-node Garage cluster; adding and removing a node
meshmonitor.md MeshMonitor with the MeshCore T096 on utilitybelt-3
uptime-kuma.md monitors in git (AutoKuma), Signal alerts, Healthchecks.io

OS updates and reboots of these hosts are done nightly by homelab-maint in talos-gitops (its docs/homelab-maint.md).