Fix stale 15-minute critical sync references — corrected to 30 minutes

critical_sync_maintenance.sh runs every 30 minutes (*/30 cron).
Three references in README.md and Partnership/README-Partnership.md
still said 15 minutes from an earlier schedule.
This commit is contained in:
Gmer4Lfe
2026-05-23 15:44:39 -04:00
parent 59c2372fa1
commit 5e4f510a42
2 changed files with 3 additions and 3 deletions
+1 -1
View File
@@ -32,7 +32,7 @@ over months — every new user, every proxy rule change, every config update app
in one place and forgotten in the other.
**The fix:** one auth stack with a managed mirror. HOST1 owns the configuration.
HOST2 runs a warm copy that stays current via 15-minute sync. HOST2's operator makes
HOST2 runs a warm copy that stays current via 30-minute sync. HOST2's operator makes
zero auth management decisions — clicking an auth container opens HOST1's WebUI via
Tailscale. Changes happen there, propagate to HOST2 in 30 minutes. One place to
manage everything for both households.
+2 -2
View File
@@ -430,7 +430,7 @@ server's own domain.
#
# HOST2 operator's experience: click NginxProxyManager in Docker UI →
# browser opens HOST1's NPM via Tailscale redirect → make changes there →
# 15 minutes later live on both servers. Zero auth management overhead on HOST2.
# 30 minutes later live on both servers. Zero auth management overhead on HOST2.
# ─────────────────────────────────────────────────────────────────────────────
```
@@ -576,7 +576,7 @@ Every minute:
Every 7 minutes:
transcode_management.sh cleanup → manager (order non-negotiable)
Every 15 minutes:
Every 30 minutes:
critical_sync_maintenance.sh Critical-Data + Emby dirty sync + partnership check
Every 30 minutes: