-
Notifications
You must be signed in to change notification settings - Fork 209
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
laravel issue on config:cache #48
Comments
@jaymoh , this isn't a bug, it is actually the expected behavior. When you run A configuration management best practice is to use the add an Then update your code to reference the config values with the |
@vino-jasuba yes, actually the problem is that this Mpesa package reads from .env file |
check out #25. I doubt it'll ever be merged in but looks like it addresses your problem. Maybe fork the repo and reference it as a private package? |
When using this SDK inside a laravel project, the package fails to read the env variables if you run the config:cache command.
It's only able to pick the MPESA secret and keys after running config:clear Which is weird because we need to be able to cache our configurations to improve on performance.
I have used the package in a couple of projects, great work. I always run config:cache and it messes me up big time.
The text was updated successfully, but these errors were encountered: