Hello @sabinem, Most changes looks good to me. What's the reason for the name changing in docker-compose.yml? I'd recommend to leave the name of the docker-compose.yml as it is instead of compose.yml as it's kind of convention across the community and when running the command it looks for this file by default.

https://github.com/search?q=docker-compose.yml&type=repositories.

@caviri I have removed the docker-compose.yml as it is now generated and have left only the compose.yml file. Does that work for you? If yes, please approve the PR.

@caviri I followed up most of your suggestions, please dev review again:

• minion was renamed to minio
• There is only one .env file as docker compose needs a .env file, since the .env file in the project root, and the env_file: field in the compose file are two different concepts, see here: https://stackoverflow.com/questions/48495663/docker-compose-env-file-not-working
• I decided agains the docker compose secrets approach, since this would not work with the current server urls that we have as mongodb://${MONGO_DB_USER}:${MONGO_DB_PASSWORD}@mongodb-instance:27017/: I tried to remove the credentials from the service urls, but ran into errors with this. Saving the credentials in .env files is a common praxis and should be okay.