Update for docker-compose v2 compatibility
Closed this issue · 1 comments
Things break with v2.
See also the possible compose v2 trailing path fix: docker/compose#8558
Error reading variables from .env:
unexpected character "@" in variable name near "iop@123.45.67.89 -p 8765\n# SSH_LOGIN should be set to the SSH Login string from WP Engine's or Kinsta's\n# admin backend. Look like this:\n# - wpengine:
iop001@iop001.ssh.wpengine.net\n# - kinsta:ssh iop001@11.22.33.44 -p 54321\n# In the above examoples the elements map like this:\n#${SSH_USER}@${SSH_HOST}\n# Each item can also be entered individually, and individual entries will take\n# precedence over components extracted from SSH_LOGIN.\n\n\nSSH_USER=\n# The user account which connects to the server. For WP Engine, this matches the\n# environment name.\n\n\nSSH_HOST=\n# The server address to connect to.\n\n\nSSH_PORT=\n# The server port listening for SSH connections\n\n\nSSH_WP_CONTENT_DIR=public/wp-content\n# default:sites/${SSH_USER}/wp-content\n# SSH_WP_CONTENT_DIR is the path to the wordpress wp-content directory. This will\n# most likely match theWP_CONTENT_DIRWordPress constant and does not include\n# a trailing slash.\n# Path can be relative to the SSH user home folder or an absolute path.\n# Examples:\n# - wpengine: sites/${SSH_USER}/wp-content\n# - kinsta: public/wp-content\n\n\nDATA_MODEL_PLUGIN=../nrmp-data-model:/var/www/html/wp-content/plugins/nrmp-data-model\nBLOCKS_PLUGIN=../nrmp-blocks:/var/www/html/wp-content/plugins/nrmp-blocks\n# Additional development plugins can be mounted into the WordPress environment as\n# individual volumes. The local relative path to the working plugin directory should\n# be pointed to the absolute path inside the container. In the following example,\n# a data-model plugin is being developed in a sibling directory to the theme:\n#\n# DATA_MODEL_PLUGIN=../example-plugin:/var/www/html/wp-content/plugins/example-plugin\n\nWORDPRESS_DEBUG=1\n"