about summary refs log tree commit homepage
path: root/examples/rails_app-2.3.4/config.ru
diff options
context:
space:
mode:
authorEric Wong <normalperson@yhbt.net>2009-11-11 19:29:57 -0800
committerEric Wong <normalperson@yhbt.net>2009-11-11 19:29:57 -0800
commit4770ea6d7a6eaf00cc19bc4fb2afd59071e8cf66 (patch)
treec8b19747254a4c0cc48511bfae8b502452e44120 /examples/rails_app-2.3.4/config.ru
parentcb90269157aeda3655b1a12ea7be4666c98a5e2c (diff)
downloadupr-4770ea6d7a6eaf00cc19bc4fb2afd59071e8cf66.tar.gz
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.
Diffstat (limited to 'examples/rails_app-2.3.4/config.ru')
-rw-r--r--examples/rails_app-2.3.4/config.ru15
1 files changed, 13 insertions, 2 deletions
diff --git a/examples/rails_app-2.3.4/config.ru b/examples/rails_app-2.3.4/config.ru
index d51b6b2..dcd7fb5 100644
--- a/examples/rails_app-2.3.4/config.ru
+++ b/examples/rails_app-2.3.4/config.ru
@@ -1,3 +1,14 @@
 require 'config/environment'
-use Rails::Rack::Static
-run ActionController::Dispatcher.new
+# upr defaults to using a Moneta::Memory backend which is good enough
+# for single-process/server applications
+$upr = Upr::Monitor.new
+
+map "/" do
+  use Rack::Chunked
+  use Rack::ContentLength
+  use Rack::Deflater
+
+  use Upr, :backend => $upr, :frequency => 1
+  use Rails::Rack::Static
+  run ActionController::Dispatcher.new
+end