@twin.org/node 0.9.2-next.1 → 0.9.2-next.11

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.
package/docs/usage.md CHANGED
@@ -25,7 +25,7 @@ npx "@twin.org/node"
25
25
  Command: help
26
26
 
27
27
  All the commands available are listed below, for more information use the --help option with a specific command.
28
- bootstrap-legacy: Bootstrap in legacy mode for backwards compatibility, **will be deprecated in future versions**
28
+ bootstrap-dev: Bootstrap the development environment
29
29
  identity-create: Create an identity
30
30
  identity-import: Import an identity
31
31
  identity-list: List all identities held in custody by the node
@@ -62,10 +62,10 @@ Key environment variables that control how the node server handles authenticatio
62
62
  | `TWIN_AUTH_API_KEY_HEADER` | `x-api-key` | HTTP header name for the API key on requests. |
63
63
  | `TWIN_AUTH_SIGNING_KEY_ID` | `auth-signing` | Vault key ID used to sign authentication JWTs. |
64
64
 
65
- ## bootstrap-legacy --help
65
+ ## bootstrap-dev --help
66
66
 
67
67
  ```text
68
- bootstrap-legacy: Bootstrap in legacy mode for backwards compatibility, **will be deprecated in future versions**
68
+ bootstrap-dev: Bootstrap the development environment
69
69
 
70
70
  env-prefix: (string, optional)
71
71
  Prefix to use for standard .env files e.g. TWIN_.
@@ -73,7 +73,7 @@ Prefix to use for standard .env files e.g. TWIN_.
73
73
  load-env: (string, optional)
74
74
  Comma separated list of paths to .env files to read input parameters from.
75
75
 
76
- Example: bootstrap-legacy --load-env=".env.bootstrap-legacy"
76
+ Example: bootstrap-dev --load-env=".env.bootstrap-dev"
77
77
  ```
78
78
 
79
79
  The command reads the following environment variables (use `load-env` to supply them from a file):
@@ -306,15 +306,15 @@ Example: tenant-list-by-org --org-id="did:iota:..."
306
306
 
307
307
  ## Example
308
308
 
309
- ### Bootstrap legacy (single command)
309
+ ### Bootstrap dev (single command)
310
310
 
311
- Runs the complete bootstrap sequence in one step using values from `.env.bootstrap-legacy`:
311
+ Runs the complete bootstrap sequence in one step using values from `.env.bootstrap-dev`:
312
312
 
313
313
  ```shell
314
- twin-node bootstrap-legacy --load-env=".env.bootstrap-legacy"
314
+ twin-node bootstrap-dev --load-env=".env.bootstrap-dev"
315
315
  ```
316
316
 
317
- The sections below show the equivalent step-by-step commands that replicate the bootstrap-legacy process.
317
+ The sections below show the equivalent step-by-step commands that replicate the bootstrap-dev process.
318
318
 
319
319
  ---
320
320
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@twin.org/node",
3
- "version": "0.9.2-next.1",
3
+ "version": "0.9.2-next.11",
4
4
  "description": "TWIN Node serving APIs using the specified configuration",
5
5
  "repository": {
6
6
  "type": "git",
@@ -14,7 +14,7 @@
14
14
  "node": ">=24.0.0"
15
15
  },
16
16
  "dependencies": {
17
- "@twin.org/node-core": "0.9.2-next.1"
17
+ "@twin.org/node-core": "0.9.2-next.11"
18
18
  },
19
19
  "bugs": {
20
20
  "url": "git+https://github.com/iotaledger/twin-node/issues"