Download the PHP package ez-php/feature-flags without Composer

On this page you can find all versions of the php package ez-php/feature-flags. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

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 PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • 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.
Please rate this library. Is it a good library?

Informations about the package feature-flags

ez-php/feature-flags

Simple feature flag evaluation for the ez-php framework. No external service required — flags are stored in a PHP file, a database table, or a plain array.


Installation

Register the provider in provider/modules.php:


Usage


Configuration

Add a config/flags.php to your application:

file must point outside config/. The framework loads every config/*.php as a config namespace, so a definitions file at config/flags.php would be this config file — the driver would then report driver and file as enabled flags and none of your real ones.

Drivers

Driver Config key value Description
file file Reads a PHP file returning array<string, bool>
database database Reads a feature_flags table via PDO
redis redis Reads feature_flags / feature_flags:contexts:<name> hashes via ext-redis
array array Empty in-memory driver (CI / test environments)

File driver

Create flags.php in your application root:

Database driver

Create the feature_flags table (example migration):

For per-context overrides (e.g. per-user beta rollouts), also create feature_flag_contexts:

When enabledFor('flag', $userId) is called, the driver checks feature_flag_contexts first; if no matching row exists, it falls back to the global feature_flags value. A missing feature_flag_contexts table is silently treated as "no overrides" — no migration is required for basic use.

Insert flags directly via SQL or through your own admin interface:

Redis driver

Same two-hash shape as the database driver's two tables:

enabledFor('beta-search', 42) checks the context hash first, then falls back to the global feature_flags hash when no override exists — identical precedence to the database driver.


Percentage rollouts

Release a flag to a stable slice of your users by adding rollouts to config/flags.php:

The bucket is crc32(flag . '|' . id) % 100, so a user stays in when you raise the percentage (10 → 25 only adds users) and different flags pick different slices. A rollout replaces the stored value for that flag; Flag::enabled('new-checkout') (no context) is only true at 100. Flags without a rollout behave as before.


Behaviour


Testing

Most tests run without external infrastructure (SQLite :memory: for the database driver, temp files for the file driver). RedisDriverTest requires a live Redis instance and is skipped automatically when ext-redis isn't loaded.


License

MIT


All versions of feature-flags with dependencies

PHP Build Version
Package Version
Requires php Version ^8.5
ez-php/contracts Version ^2.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package ez-php/feature-flags contains the following files

Loading the files please wait ...