Download the PHP package caridea/acl without Composer
On this page you can find all versions of the php package caridea/acl. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Package acl
Short Description A shrimp of an access control library
License Apache-2.0
Homepage http://github.com/libreworks/caridea-acl
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 acl
caridea-acl
Caridea is a miniscule PHP application library. This shrimpy fellow is what you'd use when you just want some helping hands and not a full-blown framework.
This is its access control component. You can create lists of permissions from any source you wish.
Installation
You can install this library using Composer:
- The master branch (version 3.x) of this project requires PHP 7.1 and has no dependencies.
- Version 2.x of this project requires PHP 7.0 and has no dependencies.
- Version 1.x of this project requires PHP 5.5 and has no dependencies.
Compliance
Releases of this library will conform to Semantic Versioning.
Our code is intended to comply with PSR-1, PSR-2, and PSR-4. If you find any issues related to standards compliance, please send a pull request!
Documentation
- Head over to Read the Docs
Definitions
Our permission API deals with three concepts: Subjects, Verbs, and Targets.
A target is something that can be protected. It has a type and an identifier. It could be a record from your database, a controller method in your application, or a URL.
A subject is a user or role that can be allowed or denied access. caridea-acl ships with two kinds of Subjects: principal and role. For instance, the currently authenticated user has a principal Subject with the username, and several role Subjects with the role names (e.g. admin, user, us-citizen).
A verb is the action the Subject can take on the Target (e.g. read, create, submit).
Target and Subject are classes, not interfaces. Since we intend ACLs to be immutable and potentially serializable, we'd rather you not add interfaces onto your own domain classes.
Examples
You must create your own ACL loaders. We include absolutely no logic to store and retrieve ACLs.
Why? Well, in our experience, the larger an application gets, the less efficient it is to serialize and store ACLs for any record that might have permissions. We've found that most of the time an application's business rules are determined by record attributes, such as who's created what record, who's the manager of a department, and so on.
By writing your own Loaders, you control in very fine detail how your permission model is provided.
Then put it all together.
You might consider wiring up all your loaders and the Service class using dependency injection, for instance with caridea/container.
