summary refs log tree commit homepage
diff options
context:
space:
mode:
authorEric Wong <normalperson@yhbt.net>2010-05-18 14:14:43 -0700
committerEric Wong <normalperson@yhbt.net>2010-05-18 14:14:43 -0700
commite78e07e0726993f7e1146518643a2b5e6eb27baa (patch)
treeb758ad2c462f2775787fef2b9e319bafea922816
parentced5c2f959f2560e904c9b82837b1a2f645b8621 (diff)
Isolate 2.0.0 appears to have quietly released, so update
the docs for it.  Fix capitalization while we're at it, too.
-rw-r--r--Sandbox14
1 files changed, 7 insertions, 7 deletions
diff --git a/Sandbox b/Sandbox
index 210add4..d2f7590 100644
--- a/Sandbox
+++ b/Sandbox
@@ -52,7 +52,7 @@ application-level libraries in unicorn/app/* (for compatibility
 with CGI-based applications, Rails <= 2.2.2, or ExecCgi).
 For now workarounds include doing one of the following:
 
-1. Isolating unicorn, setting GEM_HOME to your isolate path,
+1. Isolating unicorn, setting GEM_HOME to your Isolate path,
    and running the isolated version of unicorn.  You *must* set
    GEM_HOME before running your isolated unicorn install in this way.
 
@@ -65,14 +65,14 @@ For now workarounds include doing one of the following:
 
 === RUBYOPT pollution from SIGUSR2 upgrades
 
-With 1.x versions of isolate, it is also recommended that you
-disable it with the <tt>before_exec</tt> hook prevent the PATH and
+If you are using Isolate, using Isolate 2.x is strongly recommended as
+environment modifications are idempotent.
+
+If you are stuck with 1.x versions of Isolate, it is recommended that
+you disable it with the <tt>before_exec</tt> hook prevent the PATH and
 RUBYOPT environment variable modifications from propagating between
-upgrades in your unicorn config file:
+upgrades in your Unicorn config file:
 
         before_exec do |server|
           Isolate.disable
         end
-
-Isolate 2.x (in prerelease as of 2010.05.07) will not require this as
-environment variable modifications will be idempotent.