You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thank you for creating such a brilliant plugin.
We are in the process of setting up Visual Studio Code tasks to simplify complex docker compose commands within my team. Because we use a mono-repository, we are layering multiple compose files on top of one another, the base file which is located in a docker repository like this:
docker-compose.yaml files inside the project directories include modifications to the base compose file. Since docker/docker-compose.yaml is always the first compose file in our docker compose commands, the project name is inferred as docker regardless of which product we spin up.
We would instead like the ability to specify the --project-name argument on a task-by-task basis, such as:
First of all, thank you for creating such a brilliant plugin.
We are in the process of setting up Visual Studio Code tasks to simplify complex
docker compose
commands within my team. Because we use a mono-repository, we are layering multiple compose files on top of one another, the base file which is located in adocker
repository like this:docker-compose.yaml
files inside the project directories include modifications to the base compose file. Sincedocker/docker-compose.yaml
is always the first compose file in our docker compose commands, the project name is inferred asdocker
regardless of which product we spin up.We would instead like the ability to specify the
--project-name
argument on a task-by-task basis, such as:Using
"customOptions": "--project-name product1"
is not possible, since that will place the argument incorrectly in the resulting command:As opposed to:
If this is within scope, I would be happy to open a PR.
The text was updated successfully, but these errors were encountered: