spatie.be VS laravel-permission

How do you debug your code in PHP? Do you use var_dump or dd in Laravel? Many of us also use logger to log output & figure out the problem in multiple steps. Spatie built a debugging tool called Ray that one can use to simplify the operation over dd or logger.

When in comes to Laravel packages, the guys at Spatie are probably the kings. They have hundreds of free packages you can pick from and use into your projects. Hats down for their commitment and contribution to this beautiful ecosystem.

In this article, we'll be using the Laravel Permission package from Spatie.

I'm thinking to make it as a software license, one-time payment with one year updates, as spatie.be do.

Ray by Spatie - Debugger tool

We use Oh Dear from spatie.be to check availability, dead links, certs and more for our critical FQDNs. Works perfectly fine. we also see it as a way to give something back to them in return for all their hard work in maintaining their open-source packages for Laravel.

The guys behind it work at Spatie[1] which you have probably heard of some of their packages, and Freek has a blog[2] that has a lot of PHP stuff on - lots Laravel, and lots just general new language stuff (covering PHP8 features etc)

[1] https://spatie.be

Spatie (https://spatie.be) makes a lot of great packages for Laravel. It also has a website with video courses and the code is open-sourced here https://github.com/spatie/spatie.be. I’ve learned a lot about testing from Spatie packages.

So I along with my colleague M H Hasib started working on a project of our own inspired from the API of laravel-permissions package by Spatie and the result was mongoose-permissions package.

Examples would be something like spatie.be, beyondco.de, and serversforhackers.com

For example, let's take look at the metrics for Spatie's Laravel Permission package at the time of this writing:

I am not sure how Passport would be used for handling permissions, Passport is for authentication. I would recommend using Laravel Permission to handle your requirements. You can assign roles to users to scope out general permissions but ultimately the permissions are what should be used to limit functionality.

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".

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.

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

In this article, we'll be using the Laravel Permission package from Spatie.

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.