$MYSQL_* env vars have no effect after first startup if configs are stored on a volume

[ossimoi]

Init script seds hardcoded strings here:

misp-docker/core/files/init_misp.sh

Lines 122 to 126 in 6e3f19b

	safe_sed_i "s/localhost/$MYSQL_HOST/" $MISP_APP_CONFIG_PATH/database.php
	safe_sed_i "s/db\s*login/$MYSQL_USER/" $MISP_APP_CONFIG_PATH/database.php
	safe_sed_i "s/3306/$MYSQL_PORT/" $MISP_APP_CONFIG_PATH/database.php
	safe_sed_i "s/db\s*password/$MYSQL_PASSWORD/" $MISP_APP_CONFIG_PATH/database.php
	safe_sed_i "s/'database' => 'misp'/'database' => '$MYSQL_DATABASE'/" $MISP_APP_CONFIG_PATH/database.php

[ostefano]

Workaround is deleting configs/database.php from the host

[ossimoi]

Workaround is deleting configs/database.php from the host

Sure, but it gets annoying real fast when you don't have direct access to the host or volumes, ie. in various cloud environments.

I did not go through everything under app/Config, but is it possible to just skip mounting the config volume, assuming ENABLE_DB_SETTINGS is enabled?