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.
Download ez-php/feature-flags
More information about ez-php/feature-flags
Files in ez-php/feature-flags
Package feature-flags
Short Description Simple feature flag evaluation for the ez-php framework — File, Database, Redis, and Array drivers with a static Flag facade
License MIT
Homepage https://github.com/ez-php/feature-flags
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:
filemust point outsideconfig/. The framework loads everyconfig/*.phpas a config namespace, so a definitions file atconfig/flags.phpwould be this config file — the driver would then reportdriverandfileas 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
- Unknown flags default to
false—Flag::enabled('unknown')never throws. - Drivers never throw — all query/file failures are caught internally and result in
false. - The
Flagfacade throwsRuntimeExceptionwhen called beforeFeatureFlagServiceProviderhas been booted — this is a programmer error, not a runtime failure.
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