Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Enviroment Variables instead of parameters.yml #385

Open
ElectricMaxxx opened this issue Sep 8, 2017 · 2 comments
Open

Use Enviroment Variables instead of parameters.yml #385

ElectricMaxxx opened this issue Sep 8, 2017 · 2 comments

Comments

@ElectricMaxxx
Copy link
Member

As described in http://fabien.potencier.org/symfony4-best-practices.html we should introduce enviroment variabled over parameters.

@dbu
Copy link
Member

dbu commented Sep 8, 2017

if i read that correctly, we essentially should create a .env file to define those env variables. for local use, that seems to be the default method to do things.

@ElectricMaxxx
Copy link
Member Author

Not only. In sandbox we create a .env.dist which should be copied and customized. In website we create one for our local development and one for production.
In general, bundles served by flex will add their own parameters when loading (an config and bundle entry and ...)

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

No branches or pull requests

2 participants