- Python 96.9%
- Dockerfile 3.1%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
|
|
||
| .forgejo/workflows | ||
| .run | ||
| adb-tuner | ||
| audiobookshelf-metadata | ||
| channels-mlb | ||
| eplustv | ||
| fastchannels | ||
| freshrss | ||
| fruitdeeplinks | ||
| homelab-dashboard | ||
| homelab-utils/ha-presence-simulator | ||
| kestra | ||
| kestra-ns-files | ||
| op-python-base | ||
| pangolin | ||
| paperless | ||
| registry | ||
| tgfp | ||
| tidarr | ||
| tindra | ||
| .gitignore | ||
| a | ||
| README.md | ||
homelab-stacks
Docker Compose stacks for my homelab, managed via Komodo with GitOps auto-sync.
Structure
Each stack lives in its own directory with a docker-compose.yml and optional .env file:
stack-name/
docker-compose.yml
.env (if needed)
Deployment
Stacks are deployed to remote Docker hosts via Komodo + Periphery agents over Tailscale. Komodo syncs from this repo and manages the full lifecycle — deploy, update, rollback.
Deploy triggers
Three independent paths. Everything here is driven by a push to main — nothing in this repo is triggered by tagging a release. (The tag-triggered image builds are in the application repos, like tgfp-web. The v1.x tags on this repo are leftovers and fire nothing.)
| What | Trigger | Mechanism |
|---|---|---|
| Compose stacks | Push touching the stack's directory | Komodo polls this repo and redeploys the affected stacks |
| Kestra flows and namespace files | Push touching kestra-ns-files/** |
Forgejo webhook fires system/tenant_sync, which runs TenantSync with sourceOfTruth: GIT |
op-python-base image |
Push touching op-python-base/** |
.forgejo/workflows/build-op-python-base.yml builds on the self-hosted runner and pushes :latest to the registry |
Publishing a new op-python-base image
Commit the change under op-python-base/ and push to main:
git add op-python-base
git commit -m "..."
git push origin main
The Forgejo action logs into 192.168.192.129:3000, builds and pushes :latest. Every Kestra task runs pullPolicy: ALWAYS, so the next execution pulls it — nothing to copy onto a host. Watch the run under Actions in Forgejo; the image is live once it goes green.
Two things worth knowing:
- The path filter is the only trigger. There's no manual re-run button configured, so a rebuild with no change under
op-python-base/(to pick up a newerpython:3.13-slimoruv, say) has nothing to fire it. - A flow needing a new package must be pushed after that build is green, because the Kestra webhook and the image build watch different paths and finish at very different times. See kestra-ns-files/README.md.
Hosts
Stacks are distributed across multiple Proxmox LXC containers, each running Docker with a Periphery agent. Host assignments are configured in Komodo's server settings, not in this repo.
Notes
- All volume paths use absolute paths (required for Periphery remote deployment)
- Sensitive values go in Komodo's variable/secret management, not committed here
- Komodo polls this repo for changes; pushes trigger redeployment of affected stacks
- Kestra gets a push webhook; Komodo polls — see Deploy triggers