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
Currently, the Dev Environments feature automatically looks for the docker-compose file located at ".docker/docker-compose.yaml" in the root directory. The following are some of the downsides of doing this.
It bypasses any additional configurations that can be made
It prevents you from specifying a path to the container configuration file
It requires you to create a new docker-compose.yaml file, if you want one located in the root directory
To fix these problems, it should look for a devevironment file located at either ".docker/devenvironment.yaml" or ".devenvironment.yaml" in the root directory. You should only look for a docker-compose file if a devenvironment file is not located. By implementing this solution, not only will the problems above be fixed, but you could also implement additional features easier.
The text was updated successfully, but these errors were encountered:
@alantbarlow we're currently working of this kind solution, I would be really happy if we can plan meeting with @rumpl and we'll demo the wip. WDYT?
You can drop me an email directly [email protected]
Currently, the Dev Environments feature automatically looks for the docker-compose file located at ".docker/docker-compose.yaml" in the root directory. The following are some of the downsides of doing this.
To fix these problems, it should look for a devevironment file located at either ".docker/devenvironment.yaml" or ".devenvironment.yaml" in the root directory. You should only look for a docker-compose file if a devenvironment file is not located. By implementing this solution, not only will the problems above be fixed, but you could also implement additional features easier.
The text was updated successfully, but these errors were encountered: