Mutagen syncs should be automatically started and stopped as needed #90
Labels
enhancement
New feature or request
Milestone
Comments
|
Template init.sh script has also been updated, so as long as the latest init.sh script is on a project when 0.3.0 is released, the script will only call sync start directly on versions of Warden older than 0.3.0: |
davidalger
added a commit
that referenced
this issue
Mar 6, 2020
davidalger
added a commit
that referenced
this issue
Mar 7, 2020
…n env types not using Mutagen sessions Due to changes made to implement #90 failing to account for env types not using sync sessions, these commands would exit with the following error and a non-zero exit code: Mutagen configuration does not exist for environment type "magento1"
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On macOS (darwin) for environments that utilize Mutagen sync sessions (currently only
magento2environments leverage them, although I expect this to extend to other types fairly soon) sync should automatically start and stop when the user runsenv start,env stop,upanddown. This should also resolve issues caused whereenv up -dis run re-creatingphp-fpmcontainers breaking the sync session, as the operation would then be followed by re-creating the sync session rather than counting on the user to do so manually. Implementation of this should be such that running a start or up command does not re-create the sync session if one already exists (unless it’s broken, indicating container was re-created)The text was updated successfully, but these errors were encountered: