about summary refs log tree commit homepage
path: root/DEPLOY
diff options
context:
space:
mode:
authorEric Wong <normalperson@yhbt.net>2009-10-05 02:44:18 -0700
committerEric Wong <normalperson@yhbt.net>2009-10-05 02:47:01 -0700
commit0be3542b4e16972e0ec5ff354625f45ea8241883 (patch)
treec84ee04f6f653d9c698fd06cdbf5b9f549595e03 /DEPLOY
parentb5a0a2cce2c10ade80c1bc9a54d73194bb520776 (diff)
downloadrainbows-0be3542b4e16972e0ec5ff354625f45ea8241883.tar.gz
Diffstat (limited to 'DEPLOY')
-rw-r--r--DEPLOY29
1 files changed, 29 insertions, 0 deletions
diff --git a/DEPLOY b/DEPLOY
new file mode 100644
index 0000000..95526e2
--- /dev/null
+++ b/DEPLOY
@@ -0,0 +1,29 @@
+= Deploying \Rainbows!
+
+== nginx proxying to \Rainbows! or Unicorn
+
+For high-traffic applications, routing slow actions to \Rainbows! with
+nginx is recommended as nginx can serve static files faster and nginx
+can forward fast actions to Unicorn.
+
+          static files
+            |
+      nginx |--> slow actions --> Rainbows!
+            |
+            `--> fast actions --> Unicorn
+
+Be sure to set <tt>proxy_buffering off</tt> in nginx for "slow actions"
+if you have Comet applications (but not for Unicorn).
+
+== \Rainbows! only
+
+For the daring (or low-traffic sites), you should consider deploying
+\Rainbows! in a standalone configuration.  This will be more highly
+recommended as \Rainbows! stabilizes, especially if static file
+performance improves (or you don't need them).
+
+You will need to do this to support things like BOSH or do real-time
+processing of the request body as it is being uploaded.
+
+In this case, haproxy or any similar (non-request-body-buffering) load
+balancer should be used to balance requests between different machines.