docker/icingaweb2
6
0
Fork 0
Code Issues Actions Packages Activity

add missing changes in environment description

Browse Source
This commit is contained in:
Schreiner Pascal
2025-02-01 14:15:37 +01:00
parent 094d29b180
commit b7f61a0663
1 changed files with 10 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@@ -19,13 +19,19 @@ For a full deployment see: [comming soon ...]()
## understand environment ## understand environment
For the configuration (primarily the initial setup) I use a similar method as: https://hub.docker.com/r/icinga/icingaweb2 For the configuration (primarily the initial setup) I use a similar method as: https://hub.docker.com/r/icinga/icingaweb2
* In my case a prefix like `ICINGAWEB2_CONF` refers a configuration file. * In my case a prefix like `ICINGAWEB2_CONF` refers a configuration file.
* After the first `.` it follows the `Section` from this ini file. * As a separator I no (longer) use `.` rather `__` (2x `_`)
* After the second `.` it follows the `Key` from this `Section` before. * After the first `__` it follows the `Section` from this ini file.
* After the second `__` it follows the `Key` from this `Section` before.
* And after the `=` is comes the `value`. * And after the `=` is comes the `value`.
* As long as you don't need `.` in `Section`'s or `Key`'s you can use both spellings of docker compose environment
So will this: So will this:
``` ```
ICINGAWEB2_CONF.global.config_backend=db ICINGAWEB2_CONF__global__config_backend=db
```
or
```
ICINGAWEB2_CONF__global__config_backend: db
``` ```
create this: create this: