Phase 2 of documentation restructuring. Creates docs/reference/ with: Services (16): - alloy, argocd, borgmatic, 1password, forgejo, grafana - jellyfin, kiwix, loki, miniflux, navidrome, postgresql - prometheus, teslamate, transmission, zot Infrastructure (3): - hosts - Device inventory - tailscale - ACLs, groups, tags - routing - DNS domains and port mappings Kubernetes (2): - cluster - Minikube specs - apps - ArgoCD application registry Storage (2): - sifaka - Synology NAS configuration - backups - Backup policy All cards use wiki-links for cross-referencing and include YAML frontmatter with title and tags for Quartz. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
1.4 KiB
1.4 KiB
| title | tags | ||
|---|---|---|---|
| Transmission |
|
Transmission
BitTorrent daemon, primarily for downloading ZIM archives for kiwix.
Quick Reference
| Property | Value |
|---|---|
| URL | https://torrent.ops.eblu.me |
| Tailscale URL | https://torrent.tail8d86e.ts.net |
| Namespace | torrent |
| Image | lscr.io/linuxserver/transmission:latest |
| Storage | NFS PVC from storage/sifaka |
Storage Layout
NFS share on sifaka (/volume1/torrents):
| Path | Purpose |
|---|---|
/downloads/ |
Active downloads and metadata |
/downloads/complete/ |
Completed downloads |
/config/ |
Transmission configuration |
/watch/ |
Watch directory for .torrent files |
kiwix reads from /downloads/complete/ to serve ZIM archives.
Integration with Kiwix
The Kiwix deployment includes a torrent-sync sidecar that:
- Reads ZIM torrent list from ConfigMap
- Adds missing torrents via RPC
- Runs on startup and every 30 minutes
When downloads complete, the zim-watcher CronJob detects new ZIMs and restarts Kiwix.
Monitoring
Basic uptime via blackbox probe in alloy k8s (Services Health dashboard).
Web UI shows: active/seeding/paused counts, speeds, disk usage.
Related
- kiwix - ZIM archive consumer
- storage/sifaka - Download storage