1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
|
# rollout
Fast feature flags based on Redis.
[](https://badge.fury.io/rb/rollout)
[](https://circleci.com/gh/fetlife/rollout)
[](https://codeclimate.com/github/FetLife/rollout)
[](https://codeclimate.com/github/FetLife/rollout/coverage)
## Install it
```bash
gem install rollout
```
## How it works
Initialize a rollout object. I assign it to a global var.
```ruby
require 'redis'
$redis = Redis.new
$rollout = Rollout.new($redis)
```
or even simpler
```ruby
require 'redis'
$rollout = Rollout.new(Redis.current) # Will use REDIS_URL env var or default redis url
```
Update data specific to a feature:
```ruby
$rollout.set_feature_data(:chat, description: 'foo', release_date: 'bar', whatever: 'baz')
```
Check whether a feature is active for a particular user:
```ruby
$rollout.active?(:chat, User.first) # => true/false
```
Check whether a feature is active globally:
```ruby
$rollout.active?(:chat)
```
You can activate features using a number of different mechanisms.
## Groups
Rollout ships with one group by default: "all", which does exactly what it
sounds like.
You can activate the all group for the chat feature like this:
```ruby
$rollout.activate_group(:chat, :all)
```
You might also want to define your own groups. We have one for our caretakers:
```ruby
$rollout.define_group(:caretakers) do |user|
user.caretaker?
end
```
You can activate multiple groups per feature.
Deactivate groups like this:
```ruby
$rollout.deactivate_group(:chat, :all)
```
Groups need to be defined every time your app starts. The logic is not persisted
anywhere.
## Specific Users
You might want to let a specific user into a beta test or something. If that
user isn't part of an existing group, you can let them in specifically:
```ruby
$rollout.activate_user(:chat, @user)
```
Deactivate them like this:
```ruby
$rollout.deactivate_user(:chat, @user)
```
## User Percentages
If you're rolling out a new feature, you might want to test the waters by
slowly enabling it for a percentage of your users.
```ruby
$rollout.activate_percentage(:chat, 20)
```
The algorithm for determining which users get let in is this:
```ruby
CRC32(user.id) < (2**32 - 1) / 100.0 * percentage
```
So, for 20%, users 0, 1, 10, 11, 20, 21, etc would be allowed in. Those users
would remain in as the percentage increases.
Deactivate all percentages like this:
```ruby
$rollout.deactivate_percentage(:chat)
```
_Note that activating a feature for 100% of users will also make it active
"globally". That is when calling Rollout#active? without a user object._
In some cases you might want to have a feature activated for a random set of
users. It can come specially handy when using Rollout for split tests.
```ruby
$rollout = Rollout.new($redis, randomize_percentage: true)
```
When on `randomize_percentage` will make sure that 50% of users for feature A
are selected independently from users for feature B.
## Global actions
While groups can come in handy, the actual global setter for a feature does not require a group to be passed.
```ruby
$rollout.activate(:chat)
```
In that case you can check the global availability of a feature using the following
```ruby
$rollout.active?(:chat)
```
And if something is wrong you can set a feature off for everybody using
Deactivate everybody at once:
```ruby
$rollout.deactivate(:chat)
```
For many of our features, we keep track of error rates using redis, and
deactivate them automatically when a threshold is reached to prevent service
failures from cascading. See https://github.com/jamesgolick/degrade for the
failure detection code.
## Namespacing
Rollout separates its keys from other keys in the data store using the
"feature" keyspace.
If you're using redis, you can namespace keys further to support multiple
environments by using the
[redis-namespace](https://github.com/resque/redis-namespace) gem.
```ruby
$ns = Redis::Namespace.new(Rails.env, redis: $redis)
$rollout = Rollout.new($ns)
$rollout.activate_group(:chat, :all)
```
This example would use the "development:feature:chat:groups" key.
## Frontend / UI
* [Rollout-Dashboard](https://github.com/fiverr/rollout_dashboard/)
## Implementations in other languages
* Python: https://github.com/asenchi/proclaim
* PHP: https://github.com/opensoft/rollout
* Clojure: https://github.com/yeller/shoutout
* Perl: https://metacpan.org/pod/Toggle
## Contributors
* James Golick - Creator - https://github.com/jamesgolick
* Eric Rafaloff - Maintainer - https://github.com/EricR
## Copyright
Copyright (c) 2010-InfinityAndBeyond BitLove, Inc. See LICENSE for details.
|
