Download the PHP package vivalaz/laravel-route-restrict without Composer
On this page you can find all versions of the php package vivalaz/laravel-route-restrict. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download vivalaz/laravel-route-restrict
More information about vivalaz/laravel-route-restrict
Files in vivalaz/laravel-route-restrict
Package laravel-route-restrict
Short Description Managing project routes via roles and permissions which are assigned to users.
License MIT
Homepage https://github.com/vivalaz/laravel-route-restrict
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 laravel-route-restrict
Associate project routes with user permissions and roles
This package allows you to extend default spatie/laravel-permission behavoir and manage project routes via roles and permissions which are assigned to users.
Laravel Installation
You can install the package via composer:
The service provider will automatically get registered. Or you may manually add the service provider in your file:
Next you should publish the migration with:
After the migration has been published you can create the role- and permission-tables for routes by running the migrations:
You can publish the config file with:
When published, the config file initially contains:
Basic usage
Firstly, add the trait to your model:
This package allows for routes to be associated with user permissions and roles. (More about Roles and Permissions).
For add roles or permissions that can be accessed by user you need to create new in database. Then you can sync roles or permissions:
WARNING: If route not spicified in database, then it can be accessed by any user with any role or permission.
Using a middleware
This package comes with , and middleware. You can add them inside your file.
-
- check if user has roles that route requires. If user doesn't have any role, which are allowed for route it throws 403 Forbidden.
-
- check if user has permissions that route requires. If user doesn't have any permission, which are allowed for route it throws 403 Forbidden.
-
- check if user has roles or permissions that route requires. If user doesn't have any role or permission, which are allowed for route it throws 403 Forbidden.
Then you can protect your routes using this middleware in or .
Alternatively, you can add middleware to each route individually.
Or you can protect your controllers similarly, by setting desired middleware in the constructor:
Testing
composer test
License
The MIT License (MIT).
Copyright 2019 Grinevich Vitaly ([email protected])
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
