From c0d431d22ee1e2e69338189f9ce5a4b4abc07e6e Mon Sep 17 00:00:00 2001 From: Eric Wong Date: Sat, 10 Jan 2015 04:27:20 +0000 Subject: switch docs + website to olddoc wrongdoc was difficult to maintain because of the tidy-ffi dependency and the HTML5 changes in Darkfish could not be handled well by Tidy. olddoc is superior as it generates leaner HTML which loads faster, requires less scrolling and less processing power to render. Aesthetic comparisons are subjective of course but completely unimportant compared to speed and accessibility. The presence of images and CSS on the old (Darkfish-based) site probably set unreasonable expectations as to my ability and willingness to view such things. No more, the new website is entirely simple HTML which renders well with even the wimpiest browser (hell, olddoc even tries to generate readable raw HTML). --- DEPLOY | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'DEPLOY') diff --git a/DEPLOY b/DEPLOY index 253a068..1566d43 100644 --- a/DEPLOY +++ b/DEPLOY @@ -13,26 +13,26 @@ 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 +== 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. +can forward fast actions to unicorn. static files | nginx |--> slow actions --> Rainbows! | - `--> fast actions --> Unicorn + `--> fast actions --> unicorn Be sure to set proxy_buffering off in nginx for "slow actions" -if you have Comet applications (but not for Unicorn). +if you have Comet applications (but not for unicorn). == Denial-of-Service Concerns Since \Rainbows! is designed to talk to slow clients with long-held connections, it may be subject to brute force denial-of-service attacks. -In Unicorn and Mongrel, we've already enabled the "httpready" accept +In unicorn and Mongrel, we've already enabled the "httpready" accept filter for FreeBSD and the TCP_DEFER_ACCEPT option in Linux; but it is still possible to build clients that work around and fool these mechanisms. -- cgit v1.2.3-24-ge0c7