FailedProxy/Varaverk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Replace emby dirty sync references with play_state_sync in comments and docs

Browse Source
This commit is contained in:
Gmer4Lfe
2026-06-26 17:56:28 -04:00
parent 638aba20c0
commit 1003bee72a
4 changed files with 18 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Orchestrators/README-Orchestrators.md
+6 -6
View File
@@ -104,7 +104,7 @@ array_started.sh
# Cron — managed via Varaverk Scheduler:
*/7 * * * * transcode_management.sh
*/15 * * * * watchdog_orchestrator.sh ← resource → docker → system → stability
*/30 * * * * critical_sync_maintenance.sh ← auth + Emby dirty sync + partnership
*/30 * * * * critical_sync_maintenance.sh ← auth + play_state_sync + partnership
0 */4 * * * intermediate_sync_maintenance.sh ← arr sync + failed recovery + optional rsync
0 1 * * * daily_sync_maintenance.sh
0 7 * * 0 sunday_morning_coffee_report.sh
@@ -735,11 +735,11 @@ maintenance block before the 7am coffee report.
```bash
# ─────────────────────────────────────────────────────────────────────────────
# Two Emby syncs run in parallel — dirty and clean:
# Two Emby sync mechanisms keep the mirror current:
#
# emby-fallback dirty sync (every 30 minutes via critical_sync_maintenance.sh, Emby running):
# watch states, library deltas, user activity — continuous coverage
# WAL files excluded — safe to copy while Emby writes
# play_state_sync (every 30 minutes via critical_sync_maintenance.sh):
# API-based — syncs watched state and resume points directly via Emby API
# No rsync of live files — no WAL risk, no partial-write corruption
# HOST2 always within 30 minutes of HOST1 on playback state
#
# weekly clean sync (Sunday 2:30am, Emby stopped):
@@ -908,7 +908,7 @@ array_started.sh
*/15 * * * * watchdog_orchestrator.sh
# ─────────────────────────────────────────────────────────────────────────────
# Every 30 minutes — auth stack + Emby dirty sync + partnership check:
# Every 30 minutes — auth stack + play_state_sync + partnership check:
# ─────────────────────────────────────────────────────────────────────────────
*/30 * * * * critical_sync_maintenance.sh
Orchestrators/critical_sync_maintenance.sh
+3 -4
View File
@@ -7,10 +7,9 @@
# Schedule: */30 * * * * (every 30 minutes via User Scripts plugin)
#
# ── EXECUTION ORDER ───────────────────────────────────────────────────────────────────────────
# 1. Critical-Data rsync — auth stack, NPM config, certs (containers stopped both sides)
# 2. emby-fallback rsync — dirty Emby sync (watch states, library — Emby stays running)
# 3. CRITICAL_MAINTENANCE_SCRIPTS — any scripts configured for critical window
# 4. partnership --check — read both state files, detect changes, act accordingly
# 1. Critical-Data rsync — auth stack, NPM config, certs (containers stopped both sides)
# 2. CRITICAL_MAINTENANCE_SCRIPTS — play_state_sync + any other per-window scripts
# 3. partnership --check — read both state files, detect changes, act accordingly
#
# ── WHY EVERY 30 MINUTES ──────────────────────────────────────────────────────────────────────
# Auth stack changes (new users, proxy rules, certs) propagate within 30min ✅
Orchestrators/weekly_sync_maintenance.sh
+1 -1
View File
@@ -19,7 +19,7 @@
# Emby builds a warm image cache on HOST2 throughout the week.
# Syncing nightly resets cache — cold loads every morning for users.
# Weekly sync: cache stays warm 6 days, resets Sunday night while users sleep.
# emby-fallback dirty sync covers watch states + library every 30min between weekly syncs.
# play_state_sync covers watch/resume state every 30 min between weekly syncs.
#
# ── CONTAINER UPDATES ─────────────────────────────────────────────────────────────────────────
# Containers already stopped for sync — updates pull at zero extra downtime.