https://github.com/zephinzer/featuris
An L7 feature toggling system
https://github.com/zephinzer/featuris
Last synced: about 1 year ago
JSON representation
An L7 feature toggling system
- Host: GitHub
- URL: https://github.com/zephinzer/featuris
- Owner: zephinzer
- Created: 2017-12-07T01:29:45.000Z (over 8 years ago)
- Default Branch: master
- Last Pushed: 2017-12-18T01:56:18.000Z (over 8 years ago)
- Last Synced: 2025-02-01T18:27:21.907Z (over 1 year ago)
- Language: JavaScript
- Homepage: http://featuris.dev.joeir.net/
- Size: 89.8 KB
- Stars: 1
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Contributing: docs/contributing.md
- Roadmap: docs/roadmap.md
Awesome Lists containing this project
README
# Featuris Feature Toggling Server
An L7 feature toggling server for development teams following trunk-based development to turn on/off features through configuration instead of deployment.
## Contents
- [Getting Started](docs/getting-started.md)
- [Feature Manifests](docs/feature-manifests.md)
- [Deploying](docs/deploying.md)
- [Configuration](docs/configuration.md)
- [Integrations](docs/integrations.md)
- [Contributing](docs/contributing.md)
- [Roadmap](docs/roadmap.md)
- - -
## Feature Support
Currently supported features:
- Static flags
- A/B variant testing toggles
- Scheduled value falgs
- Acceptance flags
- Pivotal Tracker integration
### Static Flags
Static flags are hard values which should be returned. Think of these as setting the value for different environments.
### A/B Variant Flags
A/B Variant flags are used in A/B testing and can be configured to target a certain percentage of users. For example, we can release a new feature to only 10% of users by specifying the **"a"** variant to be returned 90% of the time and the **"b"** variant to be returned 10% of the time.
### Scheduled Flags
Scheduled flags are useful for seasonal banners or other time sensitive toggles and allow us to define a start and end timing for which a `true` value should be returned.
### Acceptance Flags
Acceptance flags are useful when practicing continuous delivery with trunk based development and provide a way for product owners to toggle features on/off depending on whether they have accepted user stories.