signalk-backup 0.9.1 → 0.9.3

package/README.md

@@ -71,6 +71,16 @@ Most settings live in the **webapp** under Settings. The plugin's SignalK Admin
 - `databaseExport.{questdb, grafana, signalkDatabase}` — enable per-exporter (default off; users opt in once their DB plugin is producing data)
 - `databaseExport.intervalMinutes` — how often the export tick runs (5–1440)
 
+## Backup password
+
+Your backups are always encrypted. Out of the box the engine uses a built-in default password, so backups work immediately with no setup. You can set your own password from the webapp under **Settings** at any time.
+
+Changing the password **re-keys your existing repository in place** — your existing backups are preserved, not lost. The change is rolled back automatically if anything goes wrong, so the previous password keeps working and you can never be locked out of your own backups.
+
+If you use **cloud sync** (Google Drive or SMB), the cloud copy shares the same password. After you change it, the plugin starts one sync to bring the cloud copy up to date — you don't need to re-upload everything. Until that sync finishes, don't restore from the cloud or delete your old cloud backups (they're your safety net if the sync is interrupted).
+
+If you ever see a `found existing data in storage location` error, your backups are safe — the engine just couldn't open the repository (usually a password mismatch). See [Repository recovery](https://github.com/dirkwa/signalk-backup-server#repository-recovery) in the backup-server docs.
+
 ## SignalK paths published
 
 When `emitSignalKDeltas` is on (default), the plugin publishes one delta per **scheduled** backup run (manual backups stay out of the delta stream by design). All paths sit under `vessels.<selfId>`:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "signalk-backup",
-  "version": "0.9.1",
+  "version": "0.9.3",
   "description": "Scheduled deduplicated backups of SignalK config to local storage and Google Drive (via Kopia + rclone)",
   "main": "plugin/index.js",
   "type": "module",

package/plugin/config/image-tag.d.ts

@@ -1,3 +1,3 @@
-export declare const BACKUP_SERVER_VERSION = "0.6.6";
+export declare const BACKUP_SERVER_VERSION = "0.6.10";
 export declare function resolveImageTag(tag: string): string;
 //# sourceMappingURL=image-tag.d.ts.map

package/plugin/config/image-tag.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"image-tag.d.ts","sourceRoot":"","sources":["../../src/config/image-tag.ts"],"names":[],"mappings":"AAIA,eAAO,MAAM,qBAAqB,UAAU,CAAA;AAE5C,wBAAgB,eAAe,CAAC,GAAG,EAAE,MAAM,GAAG,MAAM,CAEnD"}
+{"version":3,"file":"image-tag.d.ts","sourceRoot":"","sources":["../../src/config/image-tag.ts"],"names":[],"mappings":"AAIA,eAAO,MAAM,qBAAqB,WAAW,CAAA;AAE7C,wBAAgB,eAAe,CAAC,GAAG,EAAE,MAAM,GAAG,MAAM,CAEnD"}

package/plugin/config/image-tag.js

@@ -2,7 +2,7 @@
 // Bump this when a new signalk-backup-server release is published to ghcr.io.
 // Independent of signalk-backup's own package.json version — the two repos
 // release on independent cadences. See AGENTS.md "Gotchas" for rationale.
-export const BACKUP_SERVER_VERSION = '0.6.6';
+export const BACKUP_SERVER_VERSION = '0.6.10';
 export function resolveImageTag(tag) {
     return tag === 'auto' ? BACKUP_SERVER_VERSION : tag;
 }

package/plugin/config/image-tag.js.map

@@ -1 +1 @@
-{"version":3,"file":"image-tag.js","sourceRoot":"","sources":["../../src/config/image-tag.ts"],"names":[],"mappings":"AAAA,mEAAmE;AACnE,8EAA8E;AAC9E,2EAA2E;AAC3E,0EAA0E;AAC1E,MAAM,CAAC,MAAM,qBAAqB,GAAG,OAAO,CAAA;AAE5C,MAAM,UAAU,eAAe,CAAC,GAAW;IACzC,OAAO,GAAG,KAAK,MAAM,CAAC,CAAC,CAAC,qBAAqB,CAAC,CAAC,CAAC,GAAG,CAAA;AACrD,CAAC"}
+{"version":3,"file":"image-tag.js","sourceRoot":"","sources":["../../src/config/image-tag.ts"],"names":[],"mappings":"AAAA,mEAAmE;AACnE,8EAA8E;AAC9E,2EAA2E;AAC3E,0EAA0E;AAC1E,MAAM,CAAC,MAAM,qBAAqB,GAAG,QAAQ,CAAA;AAE7C,MAAM,UAAU,eAAe,CAAC,GAAW;IACzC,OAAO,GAAG,KAAK,MAAM,CAAC,CAAC,CAAC,qBAAqB,CAAC,CAAC,CAAC,GAAG,CAAA;AACrD,CAAC"}