Standalone Scripts
Optional one-off helper scripts for exporting, cleaning, or resetting provider data outside the app.
Standalone scripts are manual helper tools shipped with CrossWatch. They live under /scripts/.
They are not used by the app or sync engine.
Use them when you need to inspect, clean, or export/restore provider data from a shell.
If you want a rollback point, prefer the UI tool: Snapshots.
Use /scripts when you need headless workflows or automation.
"Backup" in these scripts is not a full server backup. It exports user-facing state (watchlist/history/ratings) via provider APIs. It does not dump provider databases, metadata stores, or server config. Treat it as a CrossWatch-level snapshot, not disaster recovery.
When to use scripts
Use scripts when you want to change provider-side data without changing CrossWatch.
Examples:
You tested syncs and want to undo the mess.
You are switching "source of truth" and want a clean provider baseline.
Your watch history or ratings are corrupted and you want a reset.
You want a CLI snapshot before a risky provider-side change.
These are "do it once, manually, carefully" tools.
Requirements
Scripts reuse your existing CrossWatch config at /config/config.json.
You do not re-enter credentials. Provider blocks must exist in config.json.
All standalone scripts read provider auth from config.json.
Before running a script for a provider, connect that provider in Settings → Authentication and click Save. This writes the required tokens/keys into config.json.
How to run
Open a shell in the CrossWatch container.
Go to
/scripts/.Run the script you need.
Follow the numbered menu actions.
Safety notes
Some actions are destructive on the provider side.
Create a Snapshots snapshot before resets or deletes.
If you are fixing local state, use UI tools first:
Last updated