From: Eric Wong <firstname.lastname@example.org> To: unicorn list <email@example.com> Subject: Re: [ANN] unicorn 0.99.0 - simplicity wins Date: Thu, 6 May 2010 14:01:51 -0700 [thread overview] Message-ID: <20100506210151.GB13412@dcvr.yhbt.net> (raw) In-Reply-To: <9ECF07C4-5216-47BE-961D-AFC0F0C82060@internetfamo.us> Jamie Wilkinson <firstname.lastname@example.org> wrote: > 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! Thanks for the tip! > 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?) Yeah, Unicorn will stash the original command-line it was executed with. If you need to override this at runtime, I would do something like this in the Unicorn config file: Unicorn::HttpServer::START_CTX = "/some/path/to/bin/unicorn" -- Eric Wong _______________________________________________ Unicorn mailing list - email@example.com http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying
prev parent reply other threads:[~2010-05-06 21:01 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-05-06 19:37 Eric Wong 2010-05-06 20:49 ` Jamie Wilkinson 2010-05-06 21:01 ` Eric Wong [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://yhbt.net/unicorn/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20100506210151.GB13412@dcvr.yhbt.net \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [ANN] unicorn 0.99.0 - simplicity wins' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: ../../unicorn.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).