mediact / docker-compose-development-manager

Docker Compose Development Manager

This project is ABANDONED.

Our company has moved to DDEV, for that reason this repository is deprecated.

---

Introduction

This tool allows for loading of environment variables similar to symfony/dotenv, only then for Docker Compose environments. Loading environment variable this way should help with a more consistent development process.

Installation

Checkout the project and add dev to $PATH.

Usage

Ensure docker-compose.yml, .env and .env.dev are available and configured. Then start the environment with dev up.

It's possible to install template environments from this project using dev init, which will install useful files for a quick setup.

Updating Templates

Whenever you update a file for a certain template like magento-2. You should also update the version of the docker-compose.yml. You can find it here:

x-custom:
  version: 1.x.x
  type: magento-2

Whenever you update a template in a project make sure you revert the custom changes.

You know when you have to update the templates when you see the message:

The current docker template is outdated, 
please run "dev init TEMPLATE_NAME -f" to update it.

docker-compose-development-manager's Issues

Invalid `if-else` statement in `.env.dev` file

Within the .env.dev file I get by default, there is in the bottom the following statement:

if [[ "${CONFIG__DEFAULT__SYSTEM__FULL_PAGE_CACHE__CACHING_APPLICATION}" == "2" ]]; then
    PROXY_HOST="${VARNISH_HOST}"
    PROXY_PORT="${VARNISH_PORT}"
else
    PROXY_HOST="${NGINX_PHP_FPM_HOST}"
    PROXY_PORT="${NGINX_PHP_FPM_PORT}"
fi

When entering the console container with dev console this causes a weird error for me:

unexpected character "[" in variable name near "if [[ \"${CONFIG__DEFAULT__SYSTEM__FULL_PAGE_CACHE__CACHING_APPLICATION}\" == \"2\" ]]; then\n    PROXY_HOST=\"${VARNISH_HOST}\"\n    PROXY_PORT=\"${VARNISH_PORT}\"\nelse\n    PROXY_HOST=\"${NGINX_PHP_FPM_HOST}\"\n    PROXY_PORT=\"${NGINX_PHP_FPM_PORT}\"\nfi\n"

Even though the .env.dev is fine to include in a regular bash script, it fails when using it with docker-compose. The documentation perhaps gives some clues: https://docs.docker.com/compose/env-file/ It states that the lines in the env file are only supposed to contain FOO=bar assignments, comments, but nothing else. No shell scripting. I only got it working by hard-coding the port into things instead (like the following in case Varnish is not used):

PROXY_HOST=nginx-php-fpm
PROXY_PORT=80

Service `db` requires `platform: linux/x86_64` under MacOS

While playing with this Docker setup, @WOH2021 found out that he couldn't get the db service, unless the line platform: linux/x86_64 was added to his docker-compose.yml file. He's running MacOS. The end-result would look like so:

  db:
    platform: linux/x86_64
    image: percona:8
    ...

Would this be something to be added to the docker-compose.yml file directly? Or perhaps in the docs here?

For reference: https://stackoverflow.com/questions/65456814/docker-apple-silicon-m1-preview-mysql-no-matching-manifest-for-linux-arm64-v8