Update mutagen to 0.15.0

[zolthan]

Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe

Currently we are switching to ddev having many other projects running with the latest version of mutagen (0.15.0).

So any time we are switching from any non-ddev project to dev, the daemon has to be stopped and started again.

Describe the solution you'd like

It would be nice if ddev could also use the latest version in the next release.

In addition, the new version brings much better statistics which can be used and a json formatted output for better processing.

Describe alternatives you've considered

No response

Additional context

No response

[rfay]

Hi @zolthan - I'm dragging my feet on mutagen v0.15.0 because he changed a number of the textual outputs, so it will need extensive testing, both manual etc.

Is there no way you can run v0.14 with your other projects? There are no functional differences that I'm aware of.

If you would like to do a PR that changes to v0.15.0 and try it out, you're welcome to. It's just https://github.com/drud/ddev/blob/f33e466dcac5a3ac652ce2b4e3b5818a96e39652/pkg/versionconstants/versionconstants.go#L57

But please test it before you push it up. See if it works locally. See what your experience is with it. There are some hints on how to do things in https://ddev.readthedocs.io/en/latest/developers/building-contributing/

[zolthan]

Hi @rfay,

thanks for your quick reply. For me it is enough to know that you are working on it. In my local development I'll write a small script das switches from old Docker to ddev and therefore stops the nginx proxy and mutagen daemon. Unfortunately I didn't dive into ddev deep enough to help you testing mutagen 0.15.

Best
Zolthan