kenpat
fb822d5142
- Rewrote RUNBOOK.md and DEBUG-DOCUMENTATION.md in simple 5th-grade language with real-world analogies for every technical concept - Updated README.md with current service inventory and folder map - Added cloud-migration/ subdirectory (from kitestacks-cloud-migration repo) - Added autosync/ subdirectory (from kitestacks-homelab-autosync-test repo) - Added osticket/ subdirectory (from OSTicketSystem repo) - Added cloud/ placeholder for future cloud configs - Excluded binary DB/postgres files from autosync subdirectory Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
1.6 KiB
| name | description | metadata | ||||||
|---|---|---|---|---|---|---|---|---|
| project-kitestacks | KiteStacks homelab infrastructure — Docker Compose services, networking, autosync, Forgejo repo |
|
All services run as Docker Compose stacks in /home/kenpat/docker/<app>/.
All containers join the kitestacks external Docker bridge network (172.18.0.0/16) — cloudflared uses container names as hostnames to route traffic.
Cloudflare Tunnel (token-based) routes *.kitestacks.com → containers on the kitestacks network. Tunnel ingress rules are configured in the Cloudflare Zero Trust dashboard (not in local files).
Autosync system: A systemd service (kitestacks-autosync) watches /home/kenpat/docker/ via inotify and pushes any file change to the Forgejo repo kenpat/kitestacks-homelab at gitforge.kitestacks.com. Working repo lives at /opt/kitestacks-autosync/kitestacks-homelab/. User's local clone is at /home/kenpat/forgejo-repos/kitestacks-homelab/ (remote: http://100.90.13.55:3006/kenpat/kitestacks-homelab.git). Both point to the same Forgejo repo.
Versioned docs: Autosync auto-creates docs/KiteStacks-Homelab-Documentation-v1.3.NNN.md on each change. Manual/feature docs use the next version number. Current version as of 2026-06-08: 1.3.884.
Why: User always wants changes documented and pushed to Forgejo at the end of any task.
How to apply: After making file changes, write docs to /home/kenpat/forgejo-repos/kitestacks-homelab/docs/, update CHANGELOG.md and README.md version tag, commit, and push. Use direct IP remote (no TLS issues).