examples/rails_app-2.3.4: move middleware setup to config.ru

config.ru is more obvious and easier to use with non-Rails
applications.  This is true especially if you want to share
the Upr::Monitor object/connection with the upcoming
Upr::Streaming JSON application.

1 files changed, 7 insertions, 3 deletions

diff --git a/examples/rails_app-2.3.4/config/environment.rb b/examples/rails_app-2.3.4/config/environment.rb
index c323778..f2670b8 100644
--- a/examples/rails_app-2.3.4/config/environment.rb
+++ b/examples/rails_app-2.3.4/config/environment.rb
@@ -25,8 +25,12 @@ Rails::Initializer.run do |config|
 
   # We MUST insert Upr before any parsers that read the body
   # since we need to wrap all calls to "rack.input"
-  config.middleware.insert_before('ActionController::ParamsParser',
-       'Upr',
+  # It is usually easier to just load it in RAILS_ROOT/config.ru
+  # (which is what we did, but here is a commented example of using
+  # upr inside the Rails middleware stack):
+  #
+  # config.middleware.insert_before('ActionController::ParamsParser',
+       # 'Upr',
        # The default is to use the Moneta::Memory store here.
        # This won't work right if you have multiple processes
        # serving your application, however.
@@ -48,5 +52,5 @@ Rails::Initializer.run do |config|
        # :drb => 'druby://127.0.0.1:2999',
        #
        # Update at most once every second (default is every 3 seconds)
-       :frequency => 1)
+       # :frequency => 1)
 end