[main]: Update home-server

This commit is contained in:
John Gatward committed 2026-10-06 16:57:11 +01:00
1 parent 81b43de3f1
commit 283096a43d
7 files changed
+82 -15

No files matched your search

+25 -1
View File
@@ -10,6 +10,12 @@ sources:
reference: "Ultra.cc plan, remaining capacity, rclone remote/process and enabled systemd unit, 2026-10-06"
- kind: owner-report
reference: "apt-managed rclone, active FUSE mount and Radarr/Sonarr bind-mount inspection, 2026-10-06"
- kind: owner-report
reference: "Import-then-delete intent, Remove Completed enabled, sample ratio about 0.01 and global seeding ratio limit 1, 2026-10-06"
- kind: documentation
reference: "https://wiki.servarr.com/radarr/settings#remove-completed-downloads"
- kind: documentation
reference: "https://wiki.servarr.com/sonarr/settings#remove-completed-downloads"
- kind: repository
repository: jupiter-stacks
revision: 610e325ef6a98850511ce7a089b0b9a77bfecf15
@@ -22,7 +28,9 @@ unknowns:
- total-traffic-allowance-and-reset-period
- renewal-behaviour
- rclone-cache-location-and-size-limit
- import-copy-move-and-remote-deletion-policy
- import-copy-move-settings
- qbittorrent-seeding-limit-action-and-per-torrent-overrides
- download-client-categories-and-api-removal-outcome
- mount-startup-ordering-relative-to-docker-containers
- seedbox-backup-policy
---
@@ -90,3 +98,19 @@ propagated into existing containers.
The FUSE-reported capacity is not evidence of the account quota; use the
provider allocation above.
## Import / removal
Intent: Radarr/Sonarr import required media, then remove completed downloads.
Owner reports `Completed Download Handling / Remove Completed` enabled.
qBittorrent global seeding ratio limit: `1.0`.
Reported undeleted example: share ratio approximately `0.01`; seeded less
than one minute. That ratio does not meet the configured global limit.
`Completed` download status alone does not establish completed seeding.
Upstream requirements: successful import, supported seeding goal reached,
client reports seeding complete, paused/stopped torrent, expected category.
Removal is requested through qBittorrent's API, not by deleting through rclone.
Limit action, torrent overrides and removal after reaching the goal remain
unconfirmed; no configuration change or successful-removal evidence recorded.