You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment Bolt 4 only supports one file for environment variables configuration: .env
Symfony supports overriding/extending .env based on the environment (.env.prod / env.test), and allows additional .local suffix for local changes not meant to be checked in to version control. This is really convenient.
I'd think supporting this wouldn't make anyone's existing config to break, but it will enable lots of developers with Symfony experience to use env files like they are used to.
How can you help?
I can create a pull request, It looks like this could even be a 1 line change.
The text was updated successfully, but these errors were encountered:
// The check is to ensure we don't use .env in production
if (! isset($_SERVER['APP_ENV'])) {
This doesn't mean this change will not work, and I don't see the setting of APP_ENV specified in the documentation. But it needs a second look - maybe it's only the comment that needs a change, like:
// The check is to ensure you can completely disable Dotenv loading by setting APP_ENV externally.
if (! isset($_SERVER['APP_ENV'])) {
Then it would be correct again. I've marked the PR as 'Draft' for the moment.
At the moment Bolt 4 only supports one file for environment variables configuration: .env
Symfony supports overriding/extending .env based on the environment (.env.prod / env.test), and allows additional .local suffix for local changes not meant to be checked in to version control. This is really convenient.
See:
https://symfony.com/doc/current/configuration.html#configuring-environment-variables-in-env-files
https://symfony.com/doc/current/configuration.html#overriding-environment-values-via-env-local
I'd think supporting this wouldn't make anyone's existing config to break, but it will enable lots of developers with Symfony experience to use env files like they are used to.
How can you help?
I can create a pull request, It looks like this could even be a 1 line change.
The text was updated successfully, but these errors were encountered: