Download the PHP package nusje2000/feature-toggle-bundle without Composer
On this page you can find all versions of the php package nusje2000/feature-toggle-bundle. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download nusje2000/feature-toggle-bundle
More information about nusje2000/feature-toggle-bundle
Files in nusje2000/feature-toggle-bundle
Package feature-toggle-bundle
Short Description A bundle for adding and managing feature toggles in your project
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 feature-toggle-bundle
Nusje2000/FeatureToggleBundle
Motivation
At the company I work for, we needed a way to hide unfinished features from custommers. We work with scheduled releases every week and want to deploy there versions as fast as possible. This bundle provides an implementation of feature toggles, that can be easely intergrated with the symfony framework.
We have 10+ deployed symfony projects all with their own features that can be enabled and disabled. Currently, we use the parameters.yaml file for this, but this has been proven to not be efficient. Each time we release a new feature, we have to ssh to the server and edit the file manually. This is fearly time-consuming considdering we sometimes have to do this to multiple environments on different servers.
Structure
Environments
An environment is a set of feature toggles. Let's say you have multiple projects running that all use syfmony, by using this bundle, you can have all the features acros these applications managed in one place. Multiple instances of the same applications (maybe across multiple servers) can also be seen as different environments and all can have their own set of features.
Environments when only having a single application
When just writing a simple project that will be deployed on a single server, you will just have one environment. This bundle will also covers this usecase.
Features
A feature is a component within your application, within this application a feature can have two states: disabled and enabled. A feature is coupled to an environment and different environments can have a different set of features.
Repository
Features and environments are stored in repositories. Some different repository implementations will be inculded within this bundle, but they are also easy to write yourself.
Usage
For a detailed guide on how to use this bundle, see the documentation.
All versions of feature-toggle-bundle with dependencies
psr/log Version ^1.0|^2.0|^3.0
symfony/cache Version ^6.2 || ^7.0
symfony/config Version ^6.2 || ^7.0
symfony/console Version ^6.2 || ^7.0
symfony/dependency-injection Version ^6.2 || ^7.0
symfony/event-dispatcher Version ^6.2 || ^7.0
symfony/filesystem Version ^6.2 || ^7.0
symfony/http-client Version ^6.2 || ^7.0
symfony/http-foundation Version ^6.2 || ^7.0
symfony/http-kernel Version ^6.2 || ^7.0
symfony/polyfill-php80 Version ^1.22