-
-
Notifications
You must be signed in to change notification settings - Fork 50
Replace dotenv with a built-in solution #352
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
base: master
Are you sure you want to change the base?
Conversation
vjik
commented
May 2, 2025
Q | A |
---|---|
Is bugfix? | ❌ |
New feature? | ✔️ |
Breaks BC? | ✔️ |
@@ -1,2 +1,2 @@ | |||
YII_ENV=dev | |||
YII_ENV=development |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd leave it as dev
.
'params' => [ | ||
'environments/prod/params.php', | ||
'environments/test/params.php', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can't find a way where .env files are used. Are they only for example? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Honestly, I don't like it.
Keeping env parser in each project doesn't seems as a good idea
public static function prepare(): void | ||
{ | ||
self::setEnvironment(); | ||
self::setBoolean('YII_C3', false); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
MetaStorm could be useful here :)