The new use of getenv_docker for config entries will always fall back to the default values if the environment value is empty for any reason.
It isn't uncommon to run MySQL locally as root with no password in development and testing scenarios, so this breaks a fair bit of existing implementations.
Wondering if it might make sense to align the default values with the defaults of MySQL/MariaDB for the credentials section? (This would be root as username, and an empty string as password)? Doing so would restore any existing testing setups relying on the WordPress image running on default values.
The new use of
getenv_dockerfor config entries will always fall back to the default values if the environment value is empty for any reason.It isn't uncommon to run MySQL locally as
rootwith no password in development and testing scenarios, so this breaks a fair bit of existing implementations.Wondering if it might make sense to align the default values with the defaults of MySQL/MariaDB for the credentials section? (This would be
rootas username, and an empty string as password)? Doing so would restore any existing testing setups relying on the WordPress image running on default values.