Closed facine closed 3 years ago
I have not experienced the problems @facine experienced, but it is a matter of time until I run ddev start
or ddev stop
while not in the project root. So that alone justfies some changes.
But I have experienced a problem with generating .mutagen-sync-name
that this PR fixed in an efficient manner. I have tested the modified script and it ran fine while starting/stopping ddev from both the project root and somewhere down the tree.
I experienced long waiting time when mutagen is syncing files. With the original mutagen script, the generated .mutagen-sync-name
file consisted of two lines:
drupal
null
After ddev start, the terminal shows:
Executing post-start hook...
=== Running task: Exec command 'ddev mutagen start' on the host (erik.home), output below
And this stays there for many minutes. The size of the project is not very large. Drupal core with 11 contrib modules. Which should not take more than 1 minute to sync.
I stopped waiting after 5+ minutes and tracked it down to the .mutagen-sync-name file. Normally it contains one line, but now the content of the file was as shown above. The presence of this second line ('null') causes the delay.
I have not been able to reproduce the conditions under which this occurs, but it happened 3 times in a row. After some stopping and starting, and running a test script to investigate the output of ddev describe
, the .mutagen-sync-name file now contains only one line ('drupal'). The problem did not re-occur.
This was fixed with #6
Thank you very much for your work!
I have been doing tests and I have encountered the following problems:
.ddev/.mutagen-sync-name
file, if you are not at the root of the project.I have made some changes that I hope may be helpful.
Please tell me if something is not correct.