DEPLOY FAQ HACKING LICENSE NEWS README SIGNALS Sandbox Static_Files Summary TUNING Test_Suite rainbows_1 vs_Unicorn
Rainbows ActorSpawn AppPool Base Configurator Coolio CoolioThreadPool CoolioThreadSpawn DevFdResponse Epoll EventMachine FiberPool FiberSpawn MaxBody NeverBlock Rev RevFiberSpawn RevThreadPool RevThreadSpawn Revactor Sendfile ServerToken StreamResponseEpoll ThreadPool ThreadSpawn ThreadTimeout WriterThreadPool WriterThreadSpawn XEpoll XEpollThreadPool XEpollThreadSpawn

Tips for using Rainbows! with Sandbox installation tools

Most tips for unicorn for Bundler and Isolate apply to Rainbows! as well.

TLDR (Bundler)

You need to add "rainbows" to your Gemfile for Bundler and start Rainbows! with:

bundle exec rainbows ...

TLDR (Isolate)

Isolate "rainbows" and execute the "rainbows" launcher in your isolated GEM_PATH:

$APP_ROOT/tmp/ruby-1.9/bin/rainbows ...


Due to the variety of potential dependencies, Rainbows! lazy loads many of its internals, often after the application itself is loaded. This results in more potential to interact badly with sandbox tools that modify the gem environment.

mail archives:
public: / private: