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
In order to select a subset of services by right-clicking a Compose file and selecting "Compose Up", a user has to go into their settings.json file and write:
docker.commands.composeUp: "docker-compose ${configurationFile} up ${detached} ${build} ${serviceList}"
Now that we can select services dynamically before Composing up, I'd like an option that makes this dynamic selection more accessible to use
It could follow default functionality of this feature such as "none selected" is the same as all selected etc .
Question: Does this composeUp setting in settings.json persist for all other projects the user may open up in VS Code? I feel like this may be problematic if they are a user that has a simpler Project that uses compose and also a more complex project that actually needs the subset
The text was updated successfully, but these errors were encountered:
In order to select a subset of services by right-clicking a Compose file and selecting "Compose Up", a user has to go into their settings.json file and write:
docker.commands.composeUp: "docker-compose ${configurationFile} up ${detached} ${build} ${serviceList}"
Now that we can select services dynamically before Composing up, I'd like an option that makes this dynamic selection more accessible to use
It could follow default functionality of this feature such as "none selected" is the same as all selected etc .
Question: Does this composeUp setting in settings.json persist for all other projects the user may open up in VS Code? I feel like this may be problematic if they are a user that has a simpler Project that uses compose and also a more complex project that actually needs the subset
The text was updated successfully, but these errors were encountered: