From 89841227d51977cc58e77b68309d4aef633fa61e Mon Sep 17 00:00:00 2001 From: Eric Wong Date: Tue, 4 May 2010 13:52:56 -0700 Subject: doc: DEPLOY - more strongly recommend Rainbows!-only Paragraph ordering matters psychologically. --- DEPLOY | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/DEPLOY b/DEPLOY index e04ef56..253a068 100644 --- a/DEPLOY +++ b/DEPLOY @@ -1,5 +1,18 @@ = Deploying \Rainbows! +== \Rainbows! only + +For the daring, 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. + == nginx proxying to \Rainbows! or Unicorn For high-traffic applications, routing slow actions to \Rainbows! with @@ -15,19 +28,6 @@ can forward fast actions to Unicorn. Be sure to set proxy_buffering off 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. - == Denial-of-Service Concerns Since \Rainbows! is designed to talk to slow clients with long-held -- cgit v1.2.3-24-ge0c7