Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork5.3k
Added a note about container parameters and env vars#8181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
javiereguiluz commentedJul 17, 2017
fabpot commentedJul 17, 2017
I don't understand this change. What's the solution? Just saying it does not work does not help our users. I would really prefer to fix this in Symfony instead. /cc@nicolas-grekas |
javiereguiluz commentedJul 17, 2017
There's been a misunderstandig then. Reading this note I thought you didn't want to add this feature to Dotenv:
|
fabpot commentedJul 17, 2017
This talks about validation. Here, we are talking about container parameter replacement, which can work for both regular env vars and ones coming from a .env file. |
nicolas-grekas commentedJul 17, 2017
This doesn't relate to Dotenv specifically to me: parameters are not resolved into environment vars, wherever it comes from. Or did I miss something? |
fabpot commentedJul 17, 2017
Indeed, the question is "do we want to resolve parameters for all env vars"? |
fabpot commentedSep 11, 2017
I'm closing this PR as this can be fixed thanks tosymfony/symfony#23901 |


I know that the "note" mentions the Symfony Framework and this is the component article ... but this note should go to the article mentioned in#7386, which sadly doesn't exist yet.