|
|
||
|---|---|---|
| bin | ||
| docs | ||
| examples | ||
| lib | ||
| migrations | ||
| scripts | ||
| test | ||
| website | ||
| .editorconfig | ||
| .eslintignore | ||
| .eslintrc | ||
| .gitignore | ||
| .travis.yml | ||
| app.json | ||
| CHANGELOG.md | ||
| CODE_OF_CONDUCT.md | ||
| LICENSE | ||
| logger.js | ||
| migrator.js | ||
| package.json | ||
| Procfile | ||
| README.md | ||
| server.js | ||
| yarn.lock | ||
Unleash
Unleash is a feature toggle system, that gives you a great overview over all feature toggles across all your applications and services. It comes with official client implementations for Java, Node.js, Go, Ruby and Python.
The main motivation for doing feature toggling is to decouple the process for deploying code to production and releasing new features. This helps reducing risk, and allow us to easily manage which features to enable
Feature toggles decouple deployment of code from release of new features
This repo contains the unleash-server, which contains the admin UI and a place to ask for the status of features. In order to make use of unleash you will also need a client implementation.
Online demo version available on heroku.
Activation strategies
It's fine to have a system for turning stuff on and off. But some times we want more granular control, we want to decide who to the toggle should be enabled for. This is where activation strategies comes in to the picture. Activation strategies take arbitrary config and allows us to enable a toggle in various ways.
Common activation strategies includes:
- Active For users with a specified userId
- GradualRollout to X-percent of our users
- Active for our beta users
- Active only for application instances running on host x.
Read more about activation strategies in docs/activation-strategies.md
Client implementations
We have offical SDK's for Java, Node.js, Go, Ruby and Python. And we will be happy to add implementations in other langugages written by you! These libraries makes it very easy to use Unleash in you application.
Official client SDKs:
- unleash/unleash-client-java
- unleash/unleash-client-node
- unleash/unleash-client-go
- unleash/unleash-client-ruby
- unleash/unleash-client-python
Clients written by awesome enthusiasts: 🔥
- stiano/unleash-client-dotnet (.Net Core)
- onybo/unleash-client-core (.Net Core)
- rarruda/unleash-client-python (Python 3)
The Client API
The client SDKs provides a simple abstraction making it easy to check feature toggles in your application. The code snippet below shows how you would use Unleash in Java.
if (unleash.isEnabled("AwesomeFeature")) {
//do some magic
} else {
//do old boring stuff
}
Running Unleash
Requirements
You will need a PostgreSQL 9.3+ database instance to be able to run Unleash.
When starting Unleash you must specify a database URI (can be set as environment variable DATABASE_URL) which includes a username and password, which has the rights to migrate the database.
Unleash will, at startup, check whether database migration is needed, and perform necessary migrations.
Using Unleash
The simplest way to get started: (database-url can also be set as a environment variable: DATABASE_URL)
$ npm install unleash-server -g
$ unleash -d postgres://unleash_user:password@localhost:5432/unleash -p 4242
Unleash started on http://localhost:4242
You can also require Unleash as a lib (recommended) and expand it with more options. Read more about this feature in the getting started guide.
Securing Unleash
Unleash also have extension points where you can integrate Unleash with your authentication provider (OAuth 2.0). Read more about securing unleash.
Run with docker
We have made a separate project which runs unleash inside docker. Please see unleash-docker
Developer Guide
If you want to contribute to this project you are encouraged to send issue request, or provide pull-requests. Please read the unleash developer guide to learn more on how you can contribute.