[chef] how are people using the deploy_revision resource?


Chronological Thread 
  • From: Andrew Willis < >
  • To: chef < >
  • Subject: [chef] how are people using the deploy_revision resource?
  • Date: Tue, 19 Oct 2010 16:32:13 -0400
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=e0l3aDvu6AQ2/BsYSbfSy2twJjIfFENNUO8HSZK+KHft5AR15Jmf79g6MTYcAJdhSO DddjeHUQwQVUYjiHJlzcidXozQkFCbHt62IlSD1mwTTk6xGRHWOqMuMUsLdouZcSAeR4 3e6ZFs8OG0wdV+q3alqA4OejdX3inRXMFSKsc=

Hi All,

I recently started playing around with the deploy_revision resource, and it works exactly how I expect it to. I have questions about how this would work when used with a cluster of application servers all running the same rails app. I'm betting others are using it in this configuration, and I'd love to hear more about your experience with it. When it comes time to do a deploy, do you use chef to roll out the new code to all of the servers? If so, how do you deal with the fact that the deploy may not work on a given server? Capistrano is nice in that if it can't complete each one of its tasks on each server, it rolls back the deploy. And if you aren't using chef to do your app deploys, how do you do them?


thanks!
-Andrew



Archive powered by MHonArc 2.6.16.

§