about summary refs log tree commit homepage
path: root/Sandbox
diff options
context:
space:
mode:
authorEric Wong <normalperson@yhbt.net>2011-05-01 01:44:28 +0000
committerEric Wong <normalperson@yhbt.net>2011-05-01 01:44:28 +0000
commitce4f5cd7197fb99ed99399b22cbece1684532f85 (patch)
tree1ce7e101cc19cbf47966bd2d23b7299c282d92fd /Sandbox
parent8c086f095a2f3be0f71829af9037d99c79604a37 (diff)
downloadrainbows-ce4f5cd7197fb99ed99399b22cbece1684532f85.tar.gz
Rainbows! is a bit bigger than Unicorn and usually requires
being sandboxed, too.
Diffstat (limited to 'Sandbox')
-rw-r--r--Sandbox25
1 files changed, 25 insertions, 0 deletions
diff --git a/Sandbox b/Sandbox
new file mode 100644
index 0000000..56dd29f
--- /dev/null
+++ b/Sandbox
@@ -0,0 +1,25 @@
+= Tips for using \Rainbows! with Sandbox installation tools
+
+Most {tips for Unicorn}[http://unicorn.bogomips.org/Sandbox.html]
+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 ...
+
+== Explanation
+
+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.