@alfe.ai/openclaw-sync 0.2.7 → 0.2.8
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -15,3 +15,23 @@ npm/**
|
|
|
15
15
|
extensions/**
|
|
16
16
|
# Plugin install metadata (installs.json etc.): ~/.openclaw/plugins/...
|
|
17
17
|
plugins/**
|
|
18
|
+
|
|
19
|
+
# Runtime SQLite state — MUST NOT sync. These are live databases in WAL mode;
|
|
20
|
+
# syncing the `.sqlite` file and its `-wal`/`-shm` sidecars separately uploads
|
|
21
|
+
# torn snapshots, and firstRunReconcile (cloud-wins) restores the mismatched
|
|
22
|
+
# copy on the next boot → "database disk image is malformed" → RuntimeProcess
|
|
23
|
+
# crash-loop. Zero restore value (all are rebuilt on boot from migrations).
|
|
24
|
+
# state/openclaw.sqlite = plugin state (schema_meta + installed_plugin_index)
|
|
25
|
+
# tasks/runs.sqlite = task-run history
|
|
26
|
+
# flows/registry.sqlite = flow registry
|
|
27
|
+
state/**
|
|
28
|
+
tasks/**
|
|
29
|
+
flows/**
|
|
30
|
+
|
|
31
|
+
# Chromium user-data-dir for the browser tool — same live-SQLite hazard as
|
|
32
|
+
# above (Cookies, History, Web Data, Login Data are all live WAL-mode DBs) plus
|
|
33
|
+
# hundreds of high-churn cache/profile files that exhaust the inotify watch
|
|
34
|
+
# limit. common.alfesyncignore already drops the browser *caches*; this drops
|
|
35
|
+
# the whole profile, which is ephemeral runtime state (the browser relaunches
|
|
36
|
+
# fresh) with zero cross-rebuild restore value.
|
|
37
|
+
browser/**
|