Discussion on "Guardian - Middleware based permission control for Laravel"

Emil Moe · 2016-05-05T09:19:01.000Z

I'm working on a package for permission control using middleware in Laravel. I have 3 overall goals: Exclusively defined by middleware Global and Local access Support for Saas I have already finished most of the work, but it needs more testing befo...

you are about to get a guinea pig out of me for this. Very well done. Should I attempt this in Laravel 5.2?

Yes. It should be working from Laravel 5.1, but I have only developed and tested in Laravel 5.2.31.

Thanks for showing interest, I hope it doesn't break too much ;-) I have made it on a clean install of Laravel in hope for less initial breakpoints. But any feedback is appreciated!

@emilmoe if you have tested in 5.2.31 then you should update your doc right?

There will not be anything that breaks in the minor versions 5.2.x, probably not in 5.1.x either. The newest feature it rely on is middleware parameters. Where do you think I should add a comment about it? There are still no automatic tests, only my trial and error.

I have been working on the documentation for the package, it hopefully explains how the it's intended to work. I will release some source code as soon as it's ready for it.

Feel free to give me feedback on the project so far based on the documentation and if it needs to clarify something.

http://emilmoe.com/guardian/

Note that the repo is not working now as I haven't committed anything yet

Sorry for all the grammatical errors, I didn't have too much time to read it through and wanted to post it to let you know how it's going :-)

Hi @emilmoe, this looks really good. I'm most excited about your SaaS support and Vue component as this could fit nicely into an install of Spark or other admin areas.

I agree you should change 'customers' to 'clients'.

Have you made the package public yet? How can we help you test this out?

Hi @simonhamp, thanks.

I haven't made it public yet. I have almost finished the implementation of what I call 'local' access. This means you write a middleware like guard:project.id and don't have to care more if it's a permission for all projects or that id only (where id is which variable to look for). I might change the whole projects name as I feel it collides with Laravels Guard. I'm also in good progress of making a way of telling how a permission inherit from other things. Like you might have access to a project if you have access to it's group. Right now it's a little bit mess of tables and links there, I try to make it more dynamic and less demanding for configurations.

As soon as I have these things ready I will put up a beta, you are then more than welcome to help me write automatic tests and give me feedback on the code overall. I hope it will be during this week, but I have thursday and friday off so I don't give any guarantee, but it's something I really need myself, so I put a lot of effort into it and to make it as easy as possible to implement in all kinds of projects :-)

@simonhamp I have submitted my code so far to GitHub and packagist, feel free to take a look:

https://github.com/EmilMoe/Guardian

https://packagist.org/packages/emilmoe/guardian

It's my first thing to packagist so I hope everything works.

Nice one @emilmoe. I will take a look soon!

Yeah Currently I am working on Laravel development projects and I appreciate your Idea about the utilization of Middleware as a permission control thanks for sharing this and a Keep posting...

Discussion

Guardian - Middleware based permission control for Laravel

Responses(4)

Recent in Forum

Search Hashnode

Guardian - Middleware based permission control for Laravel

Responses(4)

Recent in Forum