1 = Rainbows! - Unicorn for sleepy apps and slow clients
3 \Rainbows! is an HTTP server for sleepy Rack applications. It is based on
4 Unicorn, but designed to handle applications that expect long
5 request/response times and/or slow clients.
7 For Rack applications not heavily bound by slow external network
8 dependencies, consider Unicorn instead as it simpler and easier to
11 If you're on a small system, or write extremely tight and reliable code
12 and don't want multiple worker processes, check out
13 {Zbatery}[http://zbatery.bogomip.org/], too. Zbatery can use all the
14 crazy network concurrency options of \Rainbows! in a single worker
17 == \Rainbows! is about Diversity
19 We aim to support as many concurrency models as we can because they all
22 For network concurrency, models we currently support are:
24 * {RevFiberSpawn}[link:Rainbows/RevFiberSpawn.html]
25 * {Revactor}[link:Rainbows/Revactor.html]
26 * {ThreadPool}[link:Rainbows/ThreadPool.html]
27 * {Rev}[link:Rainbows/Rev.html]
28 * {ThreadSpawn}[link:Rainbows/ThreadSpawn.html]
29 * {EventMachine}[link:Rainbows/EventMachine.html]
30 * {RevThreadSpawn}[link:Rainbows/RevThreadSpawn.html]
31 * {FiberSpawn}[link:Rainbows/FiberSpawn.html]
32 * {FiberPool}[link:Rainbows/FiberPool.html]
33 * {NeverBlock}[link:Rainbows/NeverBlock.html]
34 * {RevThreadPool}[link:Rainbows/RevThreadPool.html]
35 * {WriterThreadPool}[link:Rainbows/WriterThreadPool.html]
36 * {WriterThreadSpawn}[link:Rainbows/WriterThreadSpawn.html]
38 We have {many more on the way}[link:TODO.html] for handling network
39 concurrency. Additionally, we also use multiple processes (managed by
40 Unicorn) for robustness and CPU/memory/disk concurrency.
42 We also provide Rainbows::AppPool Rack middleware for some network
43 concurrency models for limiting application concurrency independently of
48 * Designed for {Rack}[http://rack.rubyforge.org/], the standard for
49 modern Ruby HTTP applications.
51 * Built on {Unicorn}[http://unicorn.bogomips.org/], inheriting its
52 process/socket management features such as transparent upgrades and
53 Ruby configuration DSL.
55 * As with Unicorn, it is able to stream large request bodies off the
56 socket to the application while the client is still uploading. Since
57 \Rainbows! can handle slow clients, this feature is more useful than
60 * Combines heavyweight concurrency (worker processes) with lightweight
61 concurrency (Events/Fibers/Actors/Threads), allowing CPU/memory/disk to
62 be scaled independently of client connections. More concurrency models
63 (listed in the TODO) will be supported as we find time for them.
65 * We give you {lots of options}[link:Summary.html] with more
66 {on the way}[link:TODO.html].
70 \Rainbows! is mainly designed for the odd things Unicorn sucks at:
72 * Web Sockets (via {Sunshowers}[http://rainbows.rubyforge.org/sunshowers/])
73 * 3rd-party APIs (to services outside your control/LAN)
74 * OpenID consumers (to providers outside your control/LAN)
75 * Reverse proxy implementations with editing/censoring
76 (to upstreams outside your control/LAN)
78 * BOSH (with slow clients)
82 * real-time upload processing (via {upr}[http://upr.bogomips.org/])
84 \Rainbows! can also be used to service slow clients directly even with
89 \Rainbows! is copyright 2009 by all contributors (see logs in git).
90 It is based on Mongrel and Unicorn and carries the same license.
92 Mongrel is copyright 2007 Zed A. Shaw and contributors. It is licensed
93 under the Ruby license and the GPL2. See the included LICENSE file for
96 \Rainbows! is 100% Free Software.
100 You may download the tarball from the \Rainbows! project page on Rubyforge
101 and run setup.rb after unpacking it:
103 http://rubyforge.org/frs/?group_id=8977
105 You may also install it via RubyGems on RubyGems.org:
111 === for Rack applications
113 In APP_ROOT (where config.ru is located), run:
117 \Rainbows! will bind to all interfaces on TCP port 8080 by default.
119 === Configuration File(s)
121 \Rainbows! will look for the config.ru file used by rackup in APP_ROOT.
123 For deployments, it can use a config file for Unicorn and
124 \Rainbows!-specific options specified by the +--config-file/-c+
125 command-line switch. \Rainbows! accepts all options found in
126 {Unicorn::Configurator}[http://unicorn.bogomips.org/Unicorn/Configurator.html]
127 as well as the "\Rainbows!" block, so you can have the following in your
130 worker_processes 4 # assuming four CPU cores
133 worker_connections 100
136 See the {Rainbows! configuration}[link:Rainbows/Configurator.html]
137 {documentation}[link:Rainbows/Configurator.html]
142 You can get the latest source via git from the following locations
143 (these versions may not be stable):
145 git://git.bogomips.org/rainbows.git
146 git://repo.or.cz/rainbows.git (mirror)
148 You may browse the code from the web and download the latest snapshot
151 * http://git.bogomips.org/cgit/rainbows.git (cgit)
152 * http://repo.or.cz/w/rainbows.git (gitweb)
154 Inline patches (from "git format-patch") to the mailing list are
155 preferred because they allow code review and comments in the reply to
158 We will adhere to mostly the same conventions for patch submissions as
159 git itself. See the Documentation/SubmittingPatches document
160 distributed with git on on patch submission guidelines to follow. Just
161 don't email the git mailing list or maintainer with \Rainbows! patches.
165 There is NO WARRANTY whatsoever if anything goes wrong, but let us know
166 and we'll try our best to fix it.
170 All feedback (bug reports, user/development discussion, patches, pull
171 requests) go to the mailing list/newsgroup. Patches must be sent inline
172 (git format-patch -M + git send-email). No subscription is necessary
173 to post on the mailing list. No top posting. Address replies +To:+
176 * email: mailto:rainbows-talk@rubyforge.org
177 * nntp: nntp://news.gmane.org/gmane.comp.lang.ruby.rainbows.general
178 * subscribe: http://rubyforge.org/mailman/listinfo/rainbows-talk
179 * archives: http://rubyforge.org/pipermail/rainbows-talk