Current boot configuration will break if `php artisan config:cache` is run about shopify-app-template-php HOT 4 CLOSED

@damianed
I am not able to reproduce the problem
Run php artisan config:cache run php artisan serve

can you please provide me with all setups on my setup project both are working fine?

from shopify-app-template-php.

This issue is stale because it has been open for 90 days with no activity. It will be closed if no further action occurs in 14 days.

from shopify-app-template-php.

We are closing this issue because it has been inactive for a few months.
This probably means that it is not reproducible or it has been fixed in a newer version.
If it’s an enhancement and hasn’t been taken on since it was submitted, then it seems other issues have taken priority.

If you still encounter this issue with the latest version of this template, please reopen using the issue template. You can also contribute directly by submitting a pull request

Thank you!

from shopify-app-template-php.

I found the exact same issue today. I had to replace all the uses of env to config, then move the env calls to the appropriate config files. This is directly from Laravel's website:

If you execute the config:cache command during your deployment process, you should be sure that you are only calling the env function from within your configuration files. Once the configuration has been cached, the .env file will not be loaded; therefore, the env function will only return external, system level environment variables.

The only fix without code changes is to not use config:cache.

from shopify-app-template-php.