Download the PHP package michaelcooke/guardian without Composer
On this page you can find all versions of the php package michaelcooke/guardian. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download michaelcooke/guardian
More information about michaelcooke/guardian
Files in michaelcooke/guardian
Package guardian
Short Description A simple permissions and roles package for Laravel
License MIT
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 guardian
Guardian
Guardian is a simple permissions and roles package for Laravel that provides permissions, roles and easily configurable access inheritence.
Installing Guardian
Require Guardian via Composer
Installation is a cinch; Simply require Guardian through Composer to pull the package into your project.
Run Migrations
Then, run Guardian's migrations via Artisan.
Configure App User Model
Finally, configure Laravel to use Guardian's User model by editting the users provider configuration array in the config/auth.php.
Extend Guardian User Model
Instead of configuring Laravel to use Guardian's User model directly, you may alternatively extend Guardian's User model in app/User.php to make use of Guardian while being able to add custom relationships and attributes to your User model for your app's specific needs.
Using Guardian
Permissions
Permissions may be used to control access to particular features or functions in your application. They're defined by a key, as well as a corresponding boolean value that controls whether or not access to that permission key should be granted or blocked in all circumstances.
You're free to make these keys whatever you want, but adhering to a granular format is recommended for usage in your applications. An example for a forum section in your application may look like this:
Access
To check whether or not a user or role has access to a particular permission key, simply call hasPermission() with a permission value. It will return a boolean value based on whether or not access is granted.
Access is determined by a model's inherited and directly assigned permissions. If a model's inherited access contains permission to the key being evaluated, and no restriction exists on either the model or it's inherited access, access will be granted.
In the event of a permissions conflict with a restricted permission during an access evaluation -- due to access inheritence or otherwise -- the restriction will always take precedence and prevent access to a matching permission, regardless of whether or not permission was assigned directly to the evaulated model. This is particularly useful for a "banned" role, where a user should be barred from accessing a particular portion of your app, despite any other permissions potentially assigned.
Access Inheritence
By default, a User will inherit all permissions from any roles they are associated with; All permissions from a user's roles will trickle down and to apply to the user. Permissions obtained through inheritence are not weighed differently than directly assigned permissions.
Wildcards
Guardian uses UNIX-style glob pattern matching in permission evaluation. This grants access to several wildcard operators, the most relevant of which is * to match all characters including none at all.
More information on glob pattern matching is available on Wikipedia.
Extending Guardian
Permissible Models and the Permissible Trait
A "permissible model" is simply a model that uses the Permissible trait included with Guardian. It allows models to be associated with permissions, and inherit permissions from other permissible models.
For example, a user will inherit permissions from their associated roles out of the box. This is possible because both the user and role models use the Permissible trait, and the user model is configured to inherit permissions from any role that may be associated with the user.
Access for a particular permissible model is inherited through whatever other permissible models are defined in a model's $inheritsAccessFrom property.
