Is there a reason you don't allow this to run in CLI mode?

[hhhc]

Bug report

We need some of the settings already in CLI mode but the ServiceProvider actively prohibits that. Is there a reason for this?

[welcome[bot]]

Hello there! Thanks for opening your first issue on this repo!

Just a heads-up: Here at Backpack we use Github Issues only for tracking bugs. Talk about new features is also acceptable. This helps a lot in keeping our focus on improving Backpack. If you issue is not a bug/feature, please help us out by closing the issue yourself and posting in the appropriate medium (see below). If you're not sure where it fits, it's ok, a community member will probably reply to help you with that.

Backpack communication mediums:

• Bug Reports, Feature Requests - Github Issues (here);
• Quick help (How do I do X) - Gitter Chatroom;
• Long questions (I have done X and Y and it won't do Z wtf) - Stackoverflow, using the backpack-for-laravel tag;

Please keep in mind Backpack offers no official / paid support. Whatever help you receive here, on Gitter, Slack or Stackoverflow is thanks to our awesome awesome community members, who give up some of their time to help their peers. If you want to join our community, just start pitching in. We take pride in being a welcoming bunch.

Thank you!

-- Justin Case The Backpack Robot

[maurohmartinez]

Hi @hhhc!

Yes, there is a reason... The reason is that the package performs a db query every time the app is booted to merge the db settings with Laravel config provider. If we allow that to run in cli, a php artisan any-command would be doing that check.

I am going to close this issue since we don't plan to change how this package work at the moment. You can always register a new provider and copy the code from ours changing from "not running in console" to "running in console" check.

Cheers!