Skip to content

Conversation

gregquat
Copy link

Isn't it relevant to use the overload method when considering a .env.***.local file?
At the moment, it's difficult to override the .env value if you have to change a parameter for any reason.

It's a question, as I haven't get deeply in the component.

Isn't it relevant to use the overload method when considering a .env.***.local file?
At the moment, it's difficult to override the .env value if you have to change a parameter for any reason.

It's a question, as I haven't get deeply in the component.
@symfony-bot
Copy link

symfony-bot bot commented Nov 13, 2019

Thanks for your pull request! We love contributions.

However, this repository is what we call a "subtree split": a read-only copy of one directory of the main Symfony repository. It is used by Composer to allow developers to depend on specific Symfony components.

If you want to contribute, you should instead open a pull request on the main repository:

https://github.com/symfony/symfony

Thank you for your contribution!

PS: if you haven't already, please add tests, and beware that bug fixes should be submitted on the lowest maintained branch where they apply; only features should be submitted against the master branch.

@symfony-bot symfony-bot bot closed this Nov 13, 2019
@gregquat gregquat deleted the patch-1 branch November 13, 2019 12:31
@nicolas-grekas
Copy link
Member

Note that it already overrides the values from .env
Just give it a try.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants