[docs] #439: Mention that env variables override config file (#441)

* Mention that env variables override config file Signed-off-by: Ekaterina Mekhnetsova <[email protected]> * Update src/guide/configure/peer-configuration.md Signed-off-by: Ekaterina Mekhnetsova <[email protected]> * Update src/guide/configure/peer-configuration.md Signed-off-by: Ekaterina Mekhnetsova <[email protected]> --------- Signed-off-by: Ekaterina Mekhnetsova <[email protected]>
hyperledger-iroha · Nov 30, 2023 · adaa1b9 · adaa1b9
1 parent 2d8fb9e
commit adaa1b9
Showing 1 changed file with 6 additions and 0 deletions.
diff --git a/src/guide/configure/peer-configuration.md b/src/guide/configure/peer-configuration.md
@@ -11,6 +11,12 @@ Here's an example of how peer configuration file looks like:
 
 :::
 
+::: info
+
+Note that for convenient container deployment, configuration options specified via environment variables always override the corresponding values in the configuration file. This way, you can have a basic configuration file and also configure some options in a `docker-compose.yml` or in your shell's environment file (`.bashrc`, `.zshrc`, etc.).
+
+:::
+
 Some of the configuration options are required, while others are used for
 fine-tuning. When you create a new peer, you are required to provide the
 following: