laravel-boilerplate
laravel-permission
Our great sponsors
laravel-boilerplate | laravel-permission | |
---|---|---|
1 | 23 | |
908 | 11,779 | |
1.1% | 0.9% | |
3.3 | 9.0 | |
6 months ago | 4 days ago | |
PHP | PHP | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
laravel-boilerplate
-
Packages for Laravel
https://github.com/jeremykenedy/laravel-logger#authentication-middleware-usage https://github.com/beyondcode/laravel-dump-server https://github.com/barryvdh/laravel-debugbar https://github.com/laravel-shift/blueprint https://github.com/spatie/laravel-backup https://github.com/spatie/laravel-permission https://github.com/spatie/laravel-activitylog https://github.com/realrashid/sweet-alert https://github.com/rappasoft/laravel-livewire-tables https://github.com/yajra/laravel-datatables https://github.com/Labs64/laravel-boilerplate https://github.com/creativetimofficial/argon-dashboard-laravel https://github.com/the-control-group/voyager https://github.com/beyondcode/laravel-er-diagram-generator
laravel-permission
-
8 Essential Questions to Ask Before Using a Laravel Package
For example, let's take look at the metrics for Spatie's Laravel Permission package at the time of this writing:
-
Best way to only allow a user to view their own models?
If I remember correctly Spatie's permissions package allows for logic like "let this specific user edit models of this type" but does not allow for logic like "let this specific user edit only that specific model".
-
How do you handle different policies on one resource depending on the controller called?
Despite this I pointed in the conversation above a super interesting point made by the guys at Spatie making the Laravel permissions package, where they recommend to encapsulate the authorization logic inside policies, and it is a great way to keep things clean, but in this case its not straightforward to do so, at least not if we follow the pure "Laravel-way" of doing things.
I found interesting that the Spatie permission package recommends in their docs to include the authorization logic inside policies to encapsulate the code. But if policies are not in the equation feels like authorization ends up being spread across controllers and I didn't find the "laravel way" to do role based authorization besides gates, but even then it seems like a less refined solution than policies.
-
Packages for Laravel
https://github.com/jeremykenedy/laravel-logger#authentication-middleware-usage https://github.com/beyondcode/laravel-dump-server https://github.com/barryvdh/laravel-debugbar https://github.com/laravel-shift/blueprint https://github.com/spatie/laravel-backup https://github.com/spatie/laravel-permission https://github.com/spatie/laravel-activitylog https://github.com/realrashid/sweet-alert https://github.com/rappasoft/laravel-livewire-tables https://github.com/yajra/laravel-datatables https://github.com/Labs64/laravel-boilerplate https://github.com/creativetimofficial/argon-dashboard-laravel https://github.com/the-control-group/voyager https://github.com/beyondcode/laravel-er-diagram-generator
-
A Complete Guide To Managing User Permissions In Laravel Apps
In this article, we'll be using the Laravel Permission package from Spatie.
-
CRM for shipping company, how to develop ?
There are a few open source Laravel packages for managing roles and permissions. See https://github.com/spatie/laravel-permission or https://github.com/JosephSilber/bouncer.
-
RoleBased Permissions
Check out the Spatie Permissions package. https://github.com/spatie/laravel-permission
-
What Laravel permission package do you usually use? Does anyone come with Laravel Gate and Policy?
https://github.com/JosephSilber/bouncer and https://github.com/spatie/laravel-permission are both solid choices
-
Password + Passwordless Login in One Application
So I am building an application for a client who manages events that are staffed by volunteers from local non-profit organizations. There are four user roles (volunteer, organization manager, stand manager, and administrator) in the system of which one user can belong to many. I am using the spatie/laravel-permission package to manage these.
What are some alternatives?
laratrust - Handle roles and permissions in your Laravel application
bouncer - Laravel Eloquent roles and abilities.
LdapRecord-Laravel - Multi-domain LDAP Authentication & Management for Laravel.
sushi - Eloquent's missing "array" driver.
permission-tree - Hierarchical permissions system for Laravel apps.
tenancy - Automatic multi-tenancy for Laravel. No code changes needed.
laravel-datatables - jQuery DataTables API for Laravel
laravel-passwordless-login - A simple, safe magic login link generator for Laravel
Adldap2-Laravel - LDAP Authentication & Management for Laravel
argon-dashboard-laravel - Argon Frontend Preset For Laravel Framework 9.x and Up
PermissionManager - Admin interface for managing users, roles, permissions, using Backpack CRUD
laravel-livewire-tables - A dynamic table component for Laravel Livewire