Re: bundling/isolating: > If it is not possible to only have one Rack version installed > "globally", then they should either use Isolate or Bundler and > install a private version of Unicorn along with their preferred > version of Rack. Users who install in this way are recommended > to execute the isolated/bundled version of Unicorn, instead of > what would normally be in $PATH.
A caveat about using a bundled unicorn binary (via `bundle exec unicorn`): if you use capistrano-based deployment, make sure to use a shared vendor/bundler_gems! Obviously this is much faster than re-bundling each release, but it also prevents the unicorn binary from going missing -- if unicorn is originally executed as /app/releases/XXY/vendor/bundler_gems/bin/unicorn and that release gets rolled back or pruned by :keep_releases, the original master's binary is now gone & it will no longer be able to fork new unicorn masters (is this expected behavior/a known issue?) -jamie _______________________________________________ Unicorn mailing list - [email protected] http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying
