Meta repo for infrastructure tracking and sysadmin scripting
|
|
||
|---|---|---|
| .forgejo/workflows | ||
| .githooks | ||
| docs | ||
| issues | ||
| scripts | ||
| tests | ||
| .gitignore | ||
| .markdownlint.json | ||
| package.json | ||
| pyproject.toml | ||
| README.md | ||
Infrastructure Meta Repo
Tracking issues, scripts, and documentation for the tailnet infrastructure.
Purpose
- Issue tracking: System-level bugs (Hindsight duplicates, CUDA mismatches, provider rotation)
- Sysadmin scripts: Health checks, cleanup utilities, backup helpers, environment setup, runner supervision
- Topology docs: Tailnet service mappings, host assignments
Structure
infrastructure/
├── README.md # This file
├── issues/ # Issue templates and tracking
├── scripts/ # Re-runnable sysadmin scripts
└── docs/ # Infrastructure topology and diagrams
Quick Links
Forgejo runner supervision
Per-repo runner containers created by scripts/forgejo-runner-per-repo.sh
have no built-in supervisor. Use scripts/forgejo-runner-watchdog.sh to keep
them alive:
bash scripts/forgejo-runner-watchdog.sh once # bring every registered runner up
bash scripts/forgejo-runner-watchdog.sh list # show registered runners + container state
bash scripts/forgejo-runner-watchdog.sh install-cron # cron `once` every minute
For hosts with systemd user services, run
python3 scripts/systemd/forgejo-runner-generator.py after registering or
removing a runner so that one forgejo-runner@<repo>.service exists per
registered repo; systemctl --user enable --now forgejo-runner@<repo>.service
then keeps each container alive.