@serfab/cadre-host 1.8.0 → 1.9.0

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.
Files changed (7) hide show
  1. package/dist/orchestrator/host-process-orchestrator.d.ts +1 -1
  2. package/dist/orchestrator/host-process-orchestrator.js +1 -1
  3. package/dist/orchestrator/node-identity.d.ts +1 -1
  4. package/dist/orchestrator/node-identity.js +1 -1
  5. package/package.json +4 -4
  6. package/src/orchestrator/host-process-orchestrator.ts +1 -1
  7. package/src/orchestrator/node-identity.ts +1 -1
package/dist/orchestrator/host-process-orchestrator.d.ts CHANGED
@@ -103,7 +103,7 @@ export declare class HostProcessOrchestrator implements Orchestrator {
103
103
  * re-spawns of the same containerId), which is what makes its peer id stable
104
104
  * across restarts AND what makes its node-local stores durable: `cadre-cli
105
105
  * start` opens the file-backed bootstrap-peer, trusted-owner and strand
106
- * peer-book stores in the node's state directory, which defaults to the
106
+ * network-state stores in the node's state directory, which defaults to the
107
107
  * directory holding the `cadre.json` written here — the same workdir.
108
108
  * Terminating the loan (`removeContainer`) deletes the workdir, so the key and
109
109
  * every store go with it.
package/dist/orchestrator/host-process-orchestrator.js CHANGED
@@ -207,7 +207,7 @@ export class HostProcessOrchestrator {
207
207
  * re-spawns of the same containerId), which is what makes its peer id stable
208
208
  * across restarts AND what makes its node-local stores durable: `cadre-cli
209
209
  * start` opens the file-backed bootstrap-peer, trusted-owner and strand
210
- * peer-book stores in the node's state directory, which defaults to the
210
+ * network-state stores in the node's state directory, which defaults to the
211
211
  * directory holding the `cadre.json` written here — the same workdir.
212
212
  * Terminating the loan (`removeContainer`) deletes the workdir, so the key and
213
213
  * every store go with it.
package/dist/orchestrator/node-identity.d.ts CHANGED
@@ -7,7 +7,7 @@
7
7
  * become a stranger to the cadre that admitted it on every restart. It also
8
8
  * needs a stable on-disk home for its node-local stores — `cadre-cli start`
9
9
  * opens `FileBootstrapPeerStore` / `FileTrustedOwnerStore` /
10
- * `FileStrandPeerBookStore` in the node's state directory, which defaults to
10
+ * `FileStrandNetworkStateStore` in the node's state directory, which defaults to
11
11
  * the directory holding the config file the orchestrator writes into the workdir.
12
12
  *
13
13
  * So every managed node gets its own `identity.key` inside its workdir, written
package/dist/orchestrator/node-identity.js CHANGED
@@ -7,7 +7,7 @@
7
7
  * become a stranger to the cadre that admitted it on every restart. It also
8
8
  * needs a stable on-disk home for its node-local stores — `cadre-cli start`
9
9
  * opens `FileBootstrapPeerStore` / `FileTrustedOwnerStore` /
10
- * `FileStrandPeerBookStore` in the node's state directory, which defaults to
10
+ * `FileStrandNetworkStateStore` in the node's state directory, which defaults to
11
11
  * the directory holding the config file the orchestrator writes into the workdir.
12
12
  *
13
13
  * So every managed node gets its own `identity.key` inside its workdir, written
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@serfab/cadre-host",
3
- "version": "1.8.0",
3
+ "version": "1.9.0",
4
4
  "type": "module",
5
5
  "description": "Self-hosted cadre node manager for basement-PC deployments",
6
6
  "main": "dist/index.js",
@@ -65,9 +65,9 @@
65
65
  "@libp2p/interface": "^3.1.0",
66
66
  "@libp2p/peer-id": "^6.0.4",
67
67
  "@multiformats/multiaddr": "^12.5.1",
68
- "@serfab/cadre-cli": "^1.8.0",
69
- "@serfab/cadre-core": "^1.8.0",
70
- "@serfab/cadre-provider": "^1.8.0",
68
+ "@serfab/cadre-cli": "^1.9.0",
69
+ "@serfab/cadre-core": "^1.9.0",
70
+ "@serfab/cadre-provider": "^1.9.0",
71
71
  "commander": "^14.0.2",
72
72
  "debug": "^4.4.3",
73
73
  "fastify": "^5.7.1",
package/src/orchestrator/host-process-orchestrator.ts CHANGED
@@ -270,7 +270,7 @@ export class HostProcessOrchestrator implements Orchestrator {
270
270
  * re-spawns of the same containerId), which is what makes its peer id stable
271
271
  * across restarts AND what makes its node-local stores durable: `cadre-cli
272
272
  * start` opens the file-backed bootstrap-peer, trusted-owner and strand
273
- * peer-book stores in the node's state directory, which defaults to the
273
+ * network-state stores in the node's state directory, which defaults to the
274
274
  * directory holding the `cadre.json` written here — the same workdir.
275
275
  * Terminating the loan (`removeContainer`) deletes the workdir, so the key and
276
276
  * every store go with it.
package/src/orchestrator/node-identity.ts CHANGED
@@ -7,7 +7,7 @@
7
7
  * become a stranger to the cadre that admitted it on every restart. It also
8
8
  * needs a stable on-disk home for its node-local stores — `cadre-cli start`
9
9
  * opens `FileBootstrapPeerStore` / `FileTrustedOwnerStore` /
10
- * `FileStrandPeerBookStore` in the node's state directory, which defaults to
10
+ * `FileStrandNetworkStateStore` in the node's state directory, which defaults to
11
11
  * the directory holding the config file the orchestrator writes into the workdir.
12
12
  *
13
13
  * So every managed node gets its own `identity.key` inside its workdir, written