Environment variables moved to and replaced by env_file
Fixed warning from MySQL container
README file was updated to reflect changes in the docker compose and to remove duplicate information regarding getting started with docker run.
Moving environment variables to env_file
Current users of the docker compose file need to move their environment variables from the docker-compose.yml file to the .env file before doing docker compose up -d.
This move of environment variables should give the user more flexibility and control regarding setting up and changing the configuration. The docker-compose.yml file will also be less cluttered, while the user gets all possible environment variables in the env_file.
More info on "Fixed warning from MySQL container"
--character-set-server: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.
--collation-server: 'utf8mb3_unicode_ci' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.
This was fixed by replacing
command: --character-set-server=utf8--collation-server=utf8_unicode_ci
with
command: --character-set-server=UTF8MB4 --collation-server=UTF8MB4_unicode_ci
This will not affect current running instances.
Testing of the changes
All changes have been tested on a new setup and on a current running setup.
Test on new setup consist of following the updated instructions in the README file
Test on current setup involved using the new docker-compose.yml file and moving any current environment variables to the env_file
Updates
docker run
.Moving environment variables to env_file
Current users of the docker compose file need to move their environment variables from the
docker-compose.yml
file to the.env
file before doingdocker compose up -d
.This move of environment variables should give the user more flexibility and control regarding setting up and changing the configuration. The docker-compose.yml file will also be less cluttered, while the user gets all possible environment variables in the env_file.
More info on "Fixed warning from MySQL container"
This was fixed by replacing
command: --character-set-server=utf8--collation-server=utf8_unicode_ci
withcommand: --character-set-server=UTF8MB4 --collation-server=UTF8MB4_unicode_ci
This will not affect current running instances.Testing of the changes
All changes have been tested on a new setup and on a current running setup.