Framework: Is env function delayed?

Created on 28 Jul 2016 · 6Comments · Source: laravel/framework

Well, whenever I google about this error

[2016-07-27 15:29:08] local.ERROR: RuntimeException: No supported encrypter found. The cipher and / or key length are invalid. in C:...\vendor\laravelframework\src\Illuminate\Encryption\EncryptionServiceProvider.php:29

I found it is needed to regenerate a valid 32-length hash for AES-256-CBC. Okay, it's right.

However, I thought the ENV may be delaying to retrieve the custom data from the .env file. Because it appears again sometimes. Look at config/app.php for:

'key' => env('APP_KEY', 'someDifferentKeyFromTheDotEnvFile'),

Is it possible to decrypt the session with the wrong key at runtime?

Would OPCACHE improve that .env file reading? Is it any to do with config:cache for improvement?

Thanks in advance!

Source

hakuno

Most helpful comment

Once the config is cached, we skip reading the .env file entirely. As well as improving performance, it also fixes issues with environment variables leaking through threads.

GrahamCampbell on 28 Jul 2016

👍2

All 6 comments

Thanks for getting in touch. You just need to run the config:cache command to persist any config updates. :)

GrahamCampbell on 28 Jul 2016

Once the config is cached, we skip reading the .env file entirely. As well as improving performance, it also fixes issues with environment variables leaking through threads.

GrahamCampbell on 28 Jul 2016

👍2

Thank you so, @GrahamCampbell
Whether it's possible... so I'm not crazy :laughing: I'll rely on config:cache to solve the leaking.

hakuno on 28 Jul 2016

Hey guys, I'm having this issue from time to time. It's totally random. Every few requests, it fails reading the key from the .env file, but most of the request go through with no problems.

Running config:cache seems to do the trick, but this is on a development machine.

Is there any other way to get around this than running config:cache periodically?