ddev
Feature: `.ddev/.env.<anything>` or `.ddev/.env.global.<anything>`
Feature Request
We might want to have a way to use a unique .ddev/.env.* file for particular applications.
This specifically relates to
- #7233
They would like a Craft-specific .env that is not in the application space. It's a good idea and would improve all the CMSs that use .env, and we wouldn't be writing their file or really needing the #ddev-generated as much, although we can still request it.
Currently .ddev/.env works great for all containers, and .ddev/.env.* refers to a particular container name like .ddev/.env.solr
Think about how we should gitignore these .env files in the .ddev/ directory.
From Drupal Slack https://drupal.slack.com/archives/C5TQRQZRR/p1754664513749809
It's better not to deliver .ddev/.env.web in add-on, because other add-ons may deliver it as well.
I think we should extend the support on .ddev/.env for .ddev/.env.<anything>.<service>