Mutagen sync sessions for "local" environment type about warden HOT 3 CLOSED

@rafashkembi Was this issue intended for the project over at davidalger/warden perhaps? This project is a Magento demo environment using pre-built images, and they do not use nor require use of a mutagen session as the files for the pre-built self-contained demo are entirely within the image running the Magento application.

from warden.

Specifically about the "local" env type though, the reason that error would occur here is because Warden does not have a mutagen session configuration for anything except the "magento2" environment type. This demo environment does not inherit from the "magento2" type instead using "local" which means the entire docker-compose configuration can be found in the .warden/warden-env.yml file. If you plan on using "local" env type for other projects and want to use a mutagen configuration on those, I'd be open to a PR on the warden project adding support for including a project-specific mutagen configuration in the .warden directory of the project root.

from warden.

@rafashkembi Would be more than willing to court a PR to implement something if you care to share more regarding the use-case. For now, I'm closing this out as this is not a bug and I'm unclear on what is expected based on the original post.

from warden.