@twin.org/node 0.0.3-next.65 → 0.0.3-next.66
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/changelog.md +14 -0
- package/docs/configuration.md +11 -0
- package/docs/deployment-ec2.md +1 -1
- package/package.json +2 -2
package/docs/changelog.md
CHANGED
|
@@ -1,5 +1,19 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## [0.0.3-next.66](https://github.com/iotaledger/twin-node/compare/node-v0.0.3-next.65...node-v0.0.3-next.66) (2026-06-23)
|
|
4
|
+
|
|
5
|
+
|
|
6
|
+
### Features
|
|
7
|
+
|
|
8
|
+
* add standalone federated catalogue example config and endpoint tests ([#235](https://github.com/iotaledger/twin-node/issues/235)) ([ffb51dd](https://github.com/iotaledger/twin-node/commit/ffb51ddda5188c2f21b8ce65343b39a28f4eee4b))
|
|
9
|
+
|
|
10
|
+
|
|
11
|
+
### Dependencies
|
|
12
|
+
|
|
13
|
+
* The following workspace dependencies were updated
|
|
14
|
+
* dependencies
|
|
15
|
+
* @twin.org/node-core bumped from 0.0.3-next.65 to 0.0.3-next.66
|
|
16
|
+
|
|
3
17
|
## [0.0.3-next.65](https://github.com/iotaledger/twin-node/compare/node-v0.0.3-next.64...node-v0.0.3-next.65) (2026-06-23)
|
|
4
18
|
|
|
5
19
|
|
package/docs/configuration.md
CHANGED
|
@@ -1,5 +1,16 @@
|
|
|
1
1
|
# Node Configuration
|
|
2
2
|
|
|
3
|
+
## Available Example Configurations
|
|
4
|
+
|
|
5
|
+
Four ready-to-use example files are provided in `apps/node/`. Copy the relevant file to `.env` as a starting point:
|
|
6
|
+
|
|
7
|
+
| File | Role |
|
|
8
|
+
| ----------------------------------- | ------------------------------------------------------------------------- |
|
|
9
|
+
| `.env.example-local-entity-storage` | Full-featured node using local file/entity storage |
|
|
10
|
+
| `.env.example-aws-ec2` | Full-featured node deployed on Amazon AWS EC2 with DynamoDB |
|
|
11
|
+
| `.env.example-iota-testnet` | Full-featured node connected to the IOTA testnet |
|
|
12
|
+
| `.env.example-federated-catalogue` | Standalone federated catalogue server (no dataspace or rights management) |
|
|
13
|
+
|
|
3
14
|
## Extension Loading
|
|
4
15
|
|
|
5
16
|
The TWIN Node supports loading extensions dynamically to extend its functionality. Extensions can be loaded from multiple sources using protocol-based syntax.
|
package/docs/deployment-ec2.md
CHANGED
|
@@ -99,7 +99,7 @@ cd apps
|
|
|
99
99
|
npm install
|
|
100
100
|
npm run dist
|
|
101
101
|
cd apps/node
|
|
102
|
-
cp .env.example-entity-storage .env
|
|
102
|
+
cp .env.example-local-entity-storage .env
|
|
103
103
|
```
|
|
104
104
|
|
|
105
105
|
The .env file can be modified to suit your own use case. For example to set the location for the storage.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@twin.org/node",
|
|
3
|
-
"version": "0.0.3-next.
|
|
3
|
+
"version": "0.0.3-next.66",
|
|
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": ">=20.0.0"
|
|
15
15
|
},
|
|
16
16
|
"dependencies": {
|
|
17
|
-
"@twin.org/node-core": "0.0.3-next.
|
|
17
|
+
"@twin.org/node-core": "0.0.3-next.66"
|
|
18
18
|
},
|
|
19
19
|
"bugs": {
|
|
20
20
|
"url": "git+https://github.com/iotaledger/twin-node/issues"
|