Readme.md in optimizely_server_side-0.0.6 vs Readme.md in optimizely_server_side-0.0.7
- old
+ new
@@ -27,11 +27,11 @@
Optimizely ruby sdk provides us way to know which variation to show. But what happens when the experiment is paused ? Or there is a error happening in config.
More details about this in below section of experiment config.
### Architecture
-
### Getting Started
Add the gem in your Gemfile
@@ -123,11 +123,28 @@
end
end
end
```
+#### Don't want to stick with variation_one, variation_two ?
+You can call you own method names with `variation_` . Below i have `config.variation_best_experience` and `config.variation_pathetic_experience`.
+
+
+```ruby
+# in any app/view/foo.html.erb
+<% experiment(EXPERIMENT_KEY) do |config| %>
+ <% config.variation_best_experience(VARIATION_ONE_KEY) do %>
+ <%= render partial: 'variation_one_experience'
+ <% end %>
+
+ <% config.variation_pathetic_experience(VARIATION_DEFAULT_KEY, primary: true) do %>
+ <%= render partial: 'variation_default_experience'
+ <% end %>
+<% end %>
+
+```
In the above examples:
`EXPERIMENT_KEY`: When you will set your experiment this key will be set up that time at https://app.optimizely.com.
`VARIATION_ONE_KEY`: Key for Variation one. This will be also set when setting up experiment.
@@ -136,10 +153,10 @@
`VARIATION_DEFAULT_KEY`: Key for default experience. This will be also set when setting up experiment
`primary: true` : If you see above some variations are marked with `primary: true`. This enables handling the fallback capabilities of optimizely_server_side. If there is any error pulling datafile or experiment is paused the `primary` experience is served. Not setting primary won't give any experience during fallback times. We encourage setting it up.
-
+
### Instrumentation
This is a trial feature and may or maynot exist in future version.