Stanislav Zhuk

Rebased and moved `~/.ddev_mutagen_data_directory` to `~/.ddev/mutagen_data_directory`.

The tests look good, the only thing I'm not sure about is the previous location for `MUTAGEN_DATA_DIRECTORY=~/.ddev_mutagen_data_directory` - should we do something with it? Updated OP, ready for review.

Back to draft to make `$XDG_CONFIG_HOME` work on each OS

The problem with the timeout of the Mutagen daemon in the tests turned out to be a problem with `MUTAGEN_DATA_DIRECTORY` length: - https://github.com/mutagen-io/mutagen/issues/453 ``` Error: unable to connect to daemon:...

Okay, I'll see what I can do, I just need to find out why I broke the tests again 😅

Yes 🙂 Better to make network creation more straightforward and customizable. This may bring back the duplicate error in some cases (in docker before v25), but it's worth the sacrifice....

The product has a slightly different name, I modified the issue.

I tried to have a quick look here, but I couldn't figure it out. This error has nothing to do with Amplitude itself and occurs here, during the decoding of...

> It may be arm64 related I see this on amd64. It looks like an I/O related error, when you quickly open/close `~/.ddev/.amplitude.cache`, it may read some corrupt serialized data....

I don't mind, let's encourage people to get the latest.