Where Does Changedetection.io Store Watches?
Where changedetection.io keeps its /datastore watches, snapshots and settings.
Last updated
Changedetection.io keeps everything in /datastore: watch definitions, snapshots, settings and optional proxies.json. The official compose maps a volume there and nothing else matters for state.
CLI flags like -d override the path for bare metal runs. Proxy and browser sidecars stay stateless; only the datastore needs backup. Version pins beat latest tags for unattended updaters.
Where Changedetection stores this, by platform
<changedetection data>/datastore
/datastore mount with watches, snapshots and settings. Use bind mounts for file level backups. CLI -d flag relocates it on bare metal. Keep browser sidecars stateless.
Frequently asked questions
Changedetection forgot all watches after update. Why?
Persist /datastore as a named volume or bind mount. Unmounted containers keep watches inside throwaway storage, so updates wipe every monitored page.
Named volume or bind mount for changedetection?
Point a host path at /datastore instead of a named volume. The docs show both; bind mounts let normal backup tools grab watches, snapshots and proxies.json directly.
Notice an outdated path? Let us know.