Put the media seed behind MEDIA_SEED_ENABLED so a partner filled by other means never starts a multi-week transfer
Tier 2 beside the per-orchestrator gates. Unset reads as on — the toggle postdates the seed.
This commit is contained in:
@@ -640,6 +640,14 @@
|
||||
# WEEKLY_RSYNC_ENABLED=true ← Emby + Critical-Data still sync (NVMe)
|
||||
# MONTHLY_RSYNC_ENABLED=true ← monthly_maintenance.sh rsync section
|
||||
# FALLBACK_RSYNC_ENABLED=true ← handback writeback still works
|
||||
# MEDIA_SEED_ENABLED=false ← the onboard first-fill never starts
|
||||
#
|
||||
# MEDIA_SEED_ENABLED is the odd one out: it does not gate a schedule, it gates a single
|
||||
# multi-week transfer. Rsync/media_seed.sh pushes every DAILY_SYNC_SHARES entry to a newly
|
||||
# onboarded partner — on HOST1 that is ~28 TB against BW_LIMIT, so weeks. Turn it off when the
|
||||
# partner is going to be filled some other way (a physically moved disk, an existing library),
|
||||
# and onboard will finish without ever starting it. Turning it back on does not start anything
|
||||
# by itself; dispatch it from the Partnership tab or run the script.
|
||||
# → Run individual: bash Rsync/rsync.sh /mnt/user/Movies
|
||||
# → When ready: INTERMEDIATE_RSYNC_ENABLED=true DAILY_RSYNC_ENABLED=true
|
||||
# NOTE ON THE DEFAULT: Tier 1 ships OFF. This template is what a brand-new node is seeded from
|
||||
@@ -655,6 +663,7 @@
|
||||
WEEKLY_RSYNC_ENABLED=true # Tier 2 — weekly_sync_maintenance.sh rsync section
|
||||
MONTHLY_RSYNC_ENABLED=true # Tier 2 — monthly_maintenance.sh rsync section
|
||||
FALLBACK_RSYNC_ENABLED=true # Tier 2 — fallback.sh writeback jobs on handback
|
||||
MEDIA_SEED_ENABLED=true # Tier 2 — Rsync/media_seed.sh, the onboard first-fill
|
||||
|
||||
# ━━━ Download Webhook ━━━
|
||||
# Immediate push to remote nodes on every Sonarr/Radarr/Lidarr Download event.
|
||||
|
||||
Reference in New Issue
Block a user