My use case would be (=need to be tested) to create a task for "docker-compose up -d" i.e. start my project inside a Docker container. So, every time I'll open my project in vscode, the container will be started automatically. If so, it's really nice and will facilitate the use of "docker-compose exec xxxx" i.e. run commands inside the container (like running phpunit).
@5t3ph
thanks for the info, I can definitely envision some potential use cases for this type of configuration.
@cavo789
I'm wondering if the environment could be made even more specific, especially for Docker containers, such that scripts would be defined at either the workspace or project level to support an already ideally configured environment? I am interested to experiment further with this. 🧐
My use case would be (=need to be tested) to create a task for "docker-compose up -d" i.e. start my project inside a Docker container. So, every time I'll open my project in vscode, the container will be started automatically. If so, it's really nice and will facilitate the use of "docker-compose exec xxxx" i.e. run commands inside the container (like running phpunit).
@5t3ph thanks for the info, I can definitely envision some potential use cases for this type of configuration.
@cavo789 I'm wondering if the environment could be made even more specific, especially for Docker containers, such that scripts would be defined at either the workspace or project level to support an already ideally configured environment? I am interested to experiment further with this. 🧐
Hello, just tested and small doc written (github.com/cavo789/vscode_tips#fir...)
In my case, the how-to is not really like described in the article.
But I can confirm that, now, everytime I open my project, Docker is fired and my containers are built/loaded. And that's cool!