Closed alexxed closed 5 years ago
I am 👍 on docker.compose.options
; however, this PR removes docker.project
, which would be a backwards compatibility break. Could you maintain docker.project
as an alias for docker.composer.options
with -p
project? It is okay if docker.project
is ignored iff there is a docker.compose.options
entry.
Brief docs on this behavior would be useful.
Thanks for this enhancement.
Overview
This pull request:
Summary
For reference, the docker transport is launching a docker-compose command, for which the syntax is: docker compose [compose flags] exec [exec flags].
Before this PR, exec flags can be set in the drush alias file as a single string, this PR allows the same thing for docker-compose flags.
Description
An improvement here was recently merged in #37 but I need to specify the path to the docker compose yml file as well. I feel that the best approach is to not tie this to docker-compose arguments, so allow any arguments like it's done for the exec command.