Allow specifying the location of the .env file

At the moment this module doesn't have any config and I feel like this use case might be a bit too niche to justify introducing config. Why don't you create a custom module with a service provider where you set the dotenv.project_dir container parameter to a different value?

Or even easier, can’t you set the parameter in the services.yml file? If the service provider overrides that value, we could add a check to make sure to only set a project path if there isn’t any yet.

Hm. I wouldn't have thought it was that niche? I should think it's pretty common to have .env inside webroot, due to the variety of hosting setups.

But I can certainly create a service provider, as you suggest. If you provided a check as you describe, that would be great.

Looking at the source of the dotenv:dump command, it seems like project_dir should always be the Composer root of the project. Since we're already using DrupalFinder in the dotenv:init command, I decided to use this here as well to automatically determine the project_dir. Could you check if the changes in this MR fix the issue for you?

I also made it so dotenv.project_dir can be set in services.yml, but this shouldn't be needed for you anymore. Setting dotenv_path in composer.json also shouldn't be needed anymore.

@datawench any chance you could check if the provided solution fixes the issue for you?

Automatically closed - issue fixed for 2 weeks with no activity.