fix: remove all User Scripts dependencies — Varaverk plugin handles everything via event hooks, no User Scripts needed
This commit is contained in:
@@ -2,14 +2,15 @@
|
||||
# 📋 USER SCRIPTS PLUGIN — COMPLETE SETUP REFERENCE
|
||||
# ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
|
||||
> **Mostly superseded.** Scheduling has moved to the Varaverk plugin's built-in
|
||||
> scheduler. Only `array_started.sh` still uses User Scripts (for the "At Startup of Array"
|
||||
> hook). All cron entries are now managed via the Varaverk Scheduler tab or `schedule.json`.
|
||||
> **Fully superseded.** The Varaverk plugin handles all scheduling natively — no User
|
||||
> Scripts entries are needed. Array start and stop are triggered by the plugin's own
|
||||
> `disks_mounted` / `disks_unmounting` event hooks. Cron is managed via `schedule.json`
|
||||
> and rebuilt on every boot. User Scripts is not required.
|
||||
> See `Orchestrators/README-Orchestrators.md` for the current complete schedule.
|
||||
|
||||
**Historical reference for the User Scripts plugin setup — what each script does,
|
||||
when it ran, how it was configured.** Still useful as a script reference. Paths
|
||||
updated to reflect current boot-drive installation location.
|
||||
**Historical reference** — documents what each script does and how it was previously
|
||||
configured via User Scripts. Still useful as a script catalogue. Paths updated to
|
||||
reflect current boot-drive installation location.
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user