- From: Ash Berlin <
- Subject: [chef] Re: Re: Serial deployment
- Date: Wed, 3 Nov 2010 22:07:27 +0000
This is what we do.
Getting the particular invocation in the unicorn config file right get a number of attempts. In particular set Unicorn::HttpServer::START_CTX. The rest of the config file is pretty much a direct lift from the github's 'seamless with unicorn' post.
However saying that I can appreciate wanting something more complex.
On 3 Nov 2010, at 21:56, James Sulinski wrote:
I know this isn't exactly what you're looking for, but figured I'd toss it out there:
It's possible to do something like this using Unicorn and nginx, without removing hosts from the proxy/load balancer. This assumes that you do "smoke testing" in a staging environment prior to deploying to production. The removal/warm up/addition process is no longer necessary: unicorn is capable of rolling restarts, and nginx can skip hosts which aren't ready using the proxy_next_upstream param.
On Tue, Nov 2, 2010 at 1:38 PM, Rob Guttman <
We're just starting to use chef for managing nagios configs - so far, so good.
we would like to eventually use it for is to deploy all of our web apps
and services. A specific use case we have is to be able to *serially*
deploy to hosts/instances within a cluster behind a load balancer. For
example, we would take one host out of rotation, deploy to it, warm it
up and/or smoke test, and when warming completes and/or if smoke tests
pass then put it back into rotation and move on to the next host in the
How best to achieve that?
Archive powered by MHonArc 2.6.16.