Download the PHP package bozboz/permissions without Composer
On this page you can find all versions of the php package bozboz/permissions. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package permissions
Permissions
This package implements a basic permission system, based off the Laravel version implemented in 5.1.11.
Setup
- Add the
Bozboz\Permissions\PermissionServiceProviderclass to your app/config.php file. - Optionally add the
Bozboz\Permissions\Facades\Gatefacade to your aliases array in app/config.php. - Publish and run the migrations using
php artisan migrate:publish bozboz/permissions && php artisan migrate
Usage
First, define some rules in app/permissions.php. These are typically actions that users can do in your app.
There are 2 rule classes by default: Rule and GlobalRule. The former is for when you have a rule that relies on a context value, typically a model ID. A global rule is one that doesn't require any additional data to make sense.
Whenever you want to check a user has permission to do an action, you ask the Gate:
Alternatively, if you haven't registered the facade, you can inject the Checker object through the constructor or retrieve via the IoC container:
Note, by default, the currently authenticated user will be used to check permissions on. To authorize a specific user, pass it in:
You can also flip the check, and determine if the current user is disallowed from doing a task:
The authenticated user instance must implement Bozboz\Permissions\UserInterface. User implementations that implement this interface must define a getPermissions method. Implementations can retrieve permissions however they wish.
The rule stack
The rule stack allows permissions of varying degrees of access to be stacked together, allowing the authenticated user to match any of the defined permissions. This is useful for defining "global" permissions, and stack on more specific rules, e.g.
The stack will check the left-most rule first, then further rules defined using the then method; stopping execution when an allowed rule is found. If no rule is allowed, the method will return false.
Alternatively, a RuleStack instance can be instantiated and rules added to it using the add method:
Here, the stack will check the last added rule first, and work its way up.
