Closed taylorotwell closed 3 years ago
Hello @taylorotwell ,
Recently we added .env
files support to the RR2. The values are not updated because workers are forks and all .env
variables are inherited from the parent. When you restart the PHP worker process, the root process still has its env's
.
Is there anyway to opt out of this to the old behavior?
You can try to specify RR .env
path as an empty string, like: --dotenv=""
And also, do you use DOTENV_PATH
env variable?
Thanks - --dotenv=""
works for us.
No - I don't use DOTENV_PATH
.
Thanks -
--dotenv=""
works for us.
Great 👍🏻
@taylorotwell Feel free to close the issue then or is there something else I can help you with?
@48d90782 Update default value here: https://github.com/spiral/roadrunner-binary/blob/master/internal/cli/root.go#L87, use just empty string. To turn on this feature user should explicitly use the --dotenv
flag.
@taylorotwell Feel free to try nightly builds from here without --dotenv
: https://github.com/spiral/roadrunner-binary/actions/runs/765151263
In the upcoming 2.0.5
you can remove the --dontenv
flag, by default it will refer to the empty string.
Hello,
After 2.0.4 we are seeing our Laravel
.env
file variables persist forever in Laravel Octane powered applications. If we change variable in the Laravel.env
file we do not see the variable updated even after reloading the RoadRunner workers - a full daemon restart is required.I see 2.0.4 introduced some new
.env
functionality - we are not using that.