Panel ACL in local development
Is there a way to disable the ability for any user to access a panel when running locally and instead have the production behaviour consistently?
8 Replies
also; FWIW, that seems like a very bizarre decision. is there a reason behind the choice for it to act differently locally?
Yes. for devs experience
just switch the environment in your .env file to production and that's it
Hard disagree. How are you meant to test ACL if it just ignores it
Just set environment to production
An---yway.... I'll await confirmation that this definitely can't be disabled and then PR it in haha
I think this means only check for the env if the user model not an instance of
FilamentUser
Yeah, if it's a FilamentUser, it uses the method you have to implement, but if it's not then it falls through to app env. I think that app.env is an anti pattern, honestly. I might open a PR purely to open it up to a conversation.
Thanks for checking. Could you link me to that?
Filament\Http\Middleware\Authenticate:32