Download the PHP package ssola/enabler without Composer
On this page you can find all versions of the php package ssola/enabler. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download ssola/enabler
More information about ssola/enabler
Files in ssola/enabler
Package enabler
Short Description Enable a functionality to specific IP, specific group / users or by percentage of visitors.
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 enabler
enabler 
Enabler is a simple feature flag package. With this package you can display/hide your awesome new features to customers in order to deploy your new stuff smoothly and to have everything under control.
I would like to know what do you think about this package and if you have an idea about how to improve this package plase create a new issue.
Requirements
To use this package you only need to have:
- PHP >= 5.4
- Redis (it's our default persistence tool)
- Composer
If you need a different persistence tool like Memcache or MySQL you can simply write your own Storable adapter.
Installation
composer require ssola/enabler
composer update
How it works?
With Enabler is really simple to show/hide features to your users. Let me show how it works with this little example:
Requirement: We need to deploy our new killer feature gradually. We expect a lot of new people using it and we need to be completely sure that it works properly. At this stage we only want to enable this feature to a really small set of customers: exactly 1% of them.
First of all we have to create our new Feature and include which filters should be used.
Finally you determined to test your new Feature in a new scenario. In this respect we only want to reveal it to logged in customers.For that logic we have implemented the Identifier filter. You only have to instantiate an Identity object passing the required user data. In this case we must to pass the user id and group to which it belongs.
But now imagine that we need to display only to a bigger amount (10%) of our test-users group in a particular date range. We can do it easily adding more than one filter to the feature filter chain, like this:
Extend me
Storage
We need a storage adapter to be able to store your Feature configuration in some place. Our default storage tool is Redis, but if feel free to write your own adapters.
It's as simples as this:
Filters
At the moment we support four different filters Random Weighted Distribution, IP, Date / Date Range and Identity. But we thought people will have great ideas and it's really simple to create your own filters.
Features
You can choose among different filters or create your owns in order to displar/hide your features:
- By IP: Display your feature only to certain IP or IP range (TBD)
- By Random weight distribution: You can display your feature for example only to 10% or your visitors
- By Identity: Use our Identity class or create your own in order to have access to User Id and/or Group.
- By date or date range: Display your feature depending on specific date or set a range to display it only for a precise range of dates.
