Merge pull request #21 from iotaledger/feat/add-hornet-config-var

Add HORNET config var
iotaledger · Mar 27, 2023 · 9299736 · 9299736
2 parents f95d8d6 + e6a6de2
commit 9299736
Show file tree

Hide file tree

Showing 4 changed files with 28 additions and 7 deletions.
diff --git a/chrysalis/README.md b/chrysalis/README.md
@@ -61,7 +61,17 @@ To create this directory with correct permissions run the contained script:
 ./prepare_docker.sh
 ```
 
-### 4. Set dashboard credentials
+### 4. Select the target network
+
+By default, the `node-docker-setup` joins the `IOTA Mainnet`.
+
+If you want to switch to the `testnet`, create a file named `.env` if you did not create it already and add the following line:
+
+```
+HORNET_CONFIG_FILE=config_testnet.json
+```
+
+### 5. Set dashboard credentials
 
 To access your HORNET dashboard, a set of credentials need to be configured.
 Run the following command to generate a password hash and salt for the dashboard:
@@ -85,7 +95,7 @@ If you want to change the default `admin` username, you can add this line to you
 DASHBOARD_USERNAME=someotherusername
 ```
 
-### 5. Enable additional monitoring
+### 6. Enable additional monitoring
 
 To enable additional monitoring (cAdvisor, Prometheus, Grafana), the docker compose profile needs to be configured.
 Create a file named `.env` if you did not create it already and add the following line:

diff --git a/chrysalis/docker-compose.yml b/chrysalis/docker-compose.yml
@@ -41,7 +41,7 @@ services:
     cap_drop:
       - ALL
     volumes:
-      - ./config.json:/app/config.json:ro
+      - ./${HORNET_CONFIG_FILE:-config.json}:/app/config.json:ro
       - ./peering.json:/app/peering.json
       - ./data:/app/data
     command:

diff --git a/stardust/README.md b/stardust/README.md
@@ -63,7 +63,17 @@ To create this directory with correct permissions run the contained script:
 ./prepare_docker.sh
 ```
 
-### 4. Set dashboard credentials
+### 4. Select the target network
+
+By default, the `node-docker-setup` joins the `Shimmer` network.
+
+If you want to switch to the `testnet`, create a file named `.env` if you did not create it already and add the following line:
+
+```
+HORNET_CONFIG_FILE=config_testnet.json
+```
+
+### 5. Set dashboard credentials
 
 To access your HORNET dashboard, a set of credentials need to be configured.
 Run the following command to generate a password hash and salt for the dashboard:
@@ -87,7 +97,7 @@ If you want to change the default `admin` username, you can add this line to you
 DASHBOARD_USERNAME=someotherusername
 ```
 
-### 5. Enable additional monitoring
+### 6. Enable additional monitoring
 
 To enable additional monitoring (cAdvisor, Prometheus, Grafana), the docker compose profile needs to be configured.
 Create a file named `.env` if you did not create it already and add the following line:
@@ -96,7 +106,7 @@ Create a file named `.env` if you did not create it already and add the followin
 COMPOSE_PROFILES=monitoring
 ```
 
-### 6. Enable Wasp node
+### 7. Enable Wasp node
 
 To also run a Wasp node, the docker compose profile needs to be configured.
 Create a file named `.env` if you did not create it already and add the following line:

diff --git a/stardust/docker-compose.yml b/stardust/docker-compose.yml
@@ -38,7 +38,7 @@ services:
     cap_drop:
       - ALL
     volumes:
-      - ./config.json:/app/config.json:ro
+      - ./${HORNET_CONFIG_FILE:-config.json}:/app/config.json:ro
       - ./peering.json:/app/peering.json
       - ./data:/app/data
     command:
@@ -283,6 +283,7 @@ services:
       - "--registries.trustedPeers.filePath=/app/waspdb/trusted_peers.json"
       - "--registries.consensusState.path=/app/waspdb/chains/consensus"
       - "--wal.path=/app/waspdb/wal"
+      - "--prometheus.enabled=true"
       - "--prometheus.bindAddress=wasp:9312"
       - "--webapi.bindAddress=wasp:9090"
     profiles: