From adaa1b9d45da2849b37b977a71c291b49b234ab2 Mon Sep 17 00:00:00 2001 From: Ekaterina Mekhnetsova Date: Thu, 30 Nov 2023 15:58:50 +0100 Subject: [PATCH] [docs] #439: Mention that env variables override config file (#441) * Mention that env variables override config file Signed-off-by: Ekaterina Mekhnetsova * Update src/guide/configure/peer-configuration.md Signed-off-by: Ekaterina Mekhnetsova * Update src/guide/configure/peer-configuration.md Signed-off-by: Ekaterina Mekhnetsova --------- Signed-off-by: Ekaterina Mekhnetsova --- src/guide/configure/peer-configuration.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/src/guide/configure/peer-configuration.md b/src/guide/configure/peer-configuration.md index be013376e..565589746 100644 --- 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: