Showing the passwords hardcoded in the YAML files is a horrifically bad practice, even in a demo. Neophytes will copy this pattern - and that will then end up getting committed to a github repository. Tragedy then ensues.
Yes thanks, you can use ENV variables for passwords or external configuration files, or security vaults, or k8s secrets, read values from database, and much more. This is just for a prototype using local docker compose.
Showing the passwords hardcoded in the YAML files is a horrifically bad practice, even in a demo.
Neophytes will copy this pattern - and that will then end up getting committed to a github repository.
Tragedy then ensues.
Yes thanks, you can use ENV variables for passwords or external configuration files, or security vaults, or k8s secrets, read values from database, and much more.
This is just for a prototype using local docker compose.