-
Notifications
You must be signed in to change notification settings - Fork 903
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
Env into Config #1282
Env into Config #1282
Conversation
In many productions environments env() return null (see laravel/framework#8191). Use Config::get() is more secure. I have lost 2h to find reason for error "There is no column with name 'column_name' on table 'table_name'." and it was no table prefix, caused by null returned from env. Please merge.
BOOM! Your first PR with us, thank you so much! Someone will take a look at it shortly. Please keep in mind that:
Thank you! -- |
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.
Looks good to me!
WHOOP-WHOOP! Congrats, your first PR on this repo has officialy been merged. You should also receive an email inviting you to the Community Members team. That's where we, commited community members, debate new features and decide what's in the Backpack roadmap. Feel free to ignore the invitation if you're not interested :-) If you want to help out the community in other ways, you can:
Again. Thank you for the PR. You are a wonderful person. Keep 'em coming :-) -- P.S. Help in the Backpack community is rewarded with free Backpack commercial licenses. It's the least we can do. If you feel you've helped the community with PRs, help & other stuff, please shoot Tabacitu an email and ask him if you qualify for free licenses. You scratch my back, I scratch your back. Thank you! |
Hi @mgralikowski , I've never had this problem myself - all my environments had Thanks a lot for the PR. |
All local environments like Vagrant, Docker, Laradock has no problem with env() helper but I have two, different production servers and one works fine with env, second always return null outside config folder. The service provider made some changes on the first server few days ago, and after these works env() helpers stopped working so i recommend You avoiding env() helper ;) |
Yup, agreed - better safe :-) Cheers! |
In many productions environments env() return null (see laravel/framework#8191).
Use Config::get() is more secure. I have lost 2h to find reason for error "There is no column with name 'column_name' on table 'table_name'." and it was no table prefix, caused by null returned from env.
Please merge.