Last Updated: May 5, 2026 Priority: Conservative activation and sustained seeding health
This guide describes safe operating principles for the torrent stack without publishing tracker-identifying details or account-specific status.
- Prefer stable seeding over aggressive intake.
- Do not expand automation until upload behavior is verified.
- Keep long seed times and avoid premature cleanup.
- Use manual approval or narrow filters for risky or unknown feeds.
- Keep tracker-specific policies and credentials out of Git.
Use settings that bias toward retention and conservative throughput:
- long or unlimited seed time
- a non-trivial max seeding ratio before removal or stop
- modest concurrent download limits
- moderate active torrent limits
- categories aligned with downstream automation
Any exact values should be tuned privately based on your tracker obligations and actual upload performance.
- Verify qBittorrent is healthy and existing torrents can seed.
- Verify autobrr can reach qBittorrent.
- Add indexers in prowlarr and test them manually.
- Add IRC networks in thelounge only if needed for your workflow.
- Connect sonarr and radarr after the client and indexers are stable.
- Enable automation gradually and review results before widening scope.
Track the following privately while bringing the system online:
- overall seeding health
- hold-or-remove exposure
- upload consistency
- storage stability
- tracker-side account standing
Do not commit:
- tracker names
- tracker URLs
- IRC hosts and channels
- API keys, passkeys, authkeys, or tokens
- account ratios or warnings
- donor status or dispute history