running the example results in broken instance without login credentials. #111
Assignees
Comments
|
Hello @Leopere! Consider this example: icingaweb2 refers to the backend which has to exist of course: icingaadmin: icinga are the desired initial credentials. Best, |
|
I greatly appreciate this reply its hard to tell where to begin as someone just passing by icinga looking for where to begin and coming from the docker side. |
It seems quite complicated why is the backend not named clearer as a person who just got here I really have no idea what the difference between icinga web and icinga 2 is and if icinga db is just vanilla MySQL or if it includes any special run time magic. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
icingaweb.passwords.backend.user=pass doesn't seem to correlate with anything and https://github.com/icinga/docker-icingaweb2#usage doesn't seem to contain complete instructions. It appears that you wish to have access to a mysql/mariadb container and a redis container as well but theres no mention of this within this readme.md i've managed to braille method my way to a working login page from behind my reverse proxy with TLS termination enabled but I cannot log into anything because there appears to be no instruction on how to create the initial login account information. it seems implied that its possible but referring to the documentation it seems hard to determine how to translate whats documented into the correct docker environment variables that are required for operation.
The text was updated successfully, but these errors were encountered: