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

fix: remove all User Scripts dependencies — Varaverk plugin handles everything via event hooks, no User Scripts needed

Browse Source
This commit is contained in:
Gmer4Lfe
2026-06-01 19:57:21 -04:00
parent 98d2e6efa4
commit e0ae80d2ea
9 changed files with 65 additions and 75 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Manual.md
+15 -25
View File
@@ -30,7 +30,6 @@ Install these via **Apps** (Community Applications) on both servers:
| Plugin | Why |
|--------|-----|
| **Tailscale** | Encrypted VPN between servers — all script traffic travels over it |
| **User Scripts** | Required for "At Startup of Array" hook — array_started.sh entry only |
---
@@ -298,30 +297,24 @@ ssh -o StrictHostKeyChecking=accept-new root@unRAID-Gmer4Lfe "echo ok"
## ━━━ STEP 5: SCHEDULER SETUP ━━━
**Array start** uses the User Scripts plugin (one entry only). **Everything else** runs
through the Varaverk plugin's built-in scheduler — configure via the Scheduler tab or
`schedule.json`. Individual scripts are never scheduled directly.
**Everything runs through the Varaverk plugin's built-in scheduler** — no User Scripts
entries needed. The plugin handles all triggers natively:
- **Array start** → `Plugin/unraid/event/disks_mounted/array_start_jobs` fires `array_started.sh`
- **Array stop** → `Plugin/unraid/event/disks_unmounting/array_stop_jobs` fires `array_stopping.sh`
- **Cron** → `Plugin/unraid/event/disks_mounted/rebuild_cron` rebuilds the cron file from `schedule.json` on every boot
Configure via the Varaverk plugin Scheduler tab (or edit `schedule.json` directly).
Individual scripts are never scheduled — only orchestrators.
---
### ── User Scripts — array start only ─────────────────────────────────────────
### ── Schedule (Varaverk Scheduler) ───────────────────────────────────────────
Open **Settings → User Scripts**. Create one entry:
| Script | Schedule | Command |
|--------|----------|---------|
| `array_started` | At Array Start | `bash /boot/config/plugins/varaverk/Orchestrators/array_started.sh` |
Set to **Background Task**. This launches everything in ARRAY_START_SCRIPTS.
---
### ── Varaverk Scheduler — all cron entries ────────────────────────────────────
Configure via the Varaverk plugin Scheduler tab (or edit `schedule.json` directly):
| Script | Cron | Purpose |
|--------|------|---------|
| Script | Event/Cron | Purpose |
|--------|-----------|---------|
| `array_started` | `array_start` | All array startup scripts in order |
| `array_stopping` | `array_stop` | Ordered graceful shutdown |
| `transcode_management` | `*/7 * * * *` | Cleanup then manager — order critical |
| `watchdog_orchestrator` | `*/15 * * * *` | resource → docker → system → stability |
| `critical_sync_maintenance` | `*/30 * * * *` | auth + Emby dirty sync + partnership |
@@ -330,10 +323,7 @@ Configure via the Varaverk plugin Scheduler tab (or edit `schedule.json` directl
| `weekly_sync_maintenance` | `30 2 * * 0` | clean sync + image updates |
| `monthly_maintenance` | `0 0 15 * *` | ZFS scrub, SMART tests (uptime-gated) |
Concurrent runs are prevented by `acquire_lock` — if the previous run is still active
the new one exits immediately. No need to stagger entries manually.
For the complete schedule and what each orchestrator runs, see
Concurrent runs are prevented by `acquire_lock`. For the complete schedule see
[README-Orchestrators.md](Orchestrators/README-Orchestrators.md).
---