Randy Fay

With #3898 files created by `ddev get` are marked with #ddev-generated, so that's a step forward. So if people modify the files and remove the marker, they won't be overwritten...

Another way to mature these things would be versioning of the add-ons.

I guess you're on Ubuntu 22.04? Yes, one step at a time. Please open a new issue. I think we should install the key in the new way.

I haven't succeeded in getting a 22.04-style /usr/share/keyrings key installation to be trusted. Tried ``` curl -fsSL https://apt.fury.io/drud/gpg.key | sudo tee /usr/share/keyrings/ddev.gpg >/dev/null echo "deb [signed-by=/usr/share/keyrings/ddev.gpg] https://apt.fury.io/drud/ * *" |...

Thanks for this! I imagine you're queueing up a PR for this, but reading this issue it's not clear to me what you want to do.

It's happy to write files, and ddev writes oh-so-many. This is the equivalent of what is done in settings.ddev.php. I imagine there's a reason that I did this in Laravel...

I have a little custom command named "vars" that I use for checking these things: ``` $ cat vars #!/bin/bash set | grep DDEV ``` It should work fine on...

Would love to have you do a PR @mandrasch !

The normal solution for people who have specific settings expectations is just to turn off settings management, `disable_settings_management: true`. Is this your situation? Please take a look at https://ddev.readthedocs.io/en/latest/users/topics/cms_specific_help/ and...

I hope you read https://ddev.readthedocs.io/en/latest/users/topics/cms_specific_help/ and undestand that you can also remove the `#ddev-generated` from AdditionalConfiguration.php and do whatever you want with it.