General discussion about Chef

rails app deployment


Chronological Thread 
  • From: Ian Kallen <spidaman.list@gmail.com>
  • To: chef@lists.opscode.com
  • Subject: rails app deployment
  • Date: Fri, 17 Apr 2009 09:18:26 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=DcXZwrilAvwGO7g+ODEucNGOVlDGfqV49bV/35YUgEEIt28W4DUWR5YX+XSXu1S4H1 rEDq844zv++QkUvKcgUB9vGIEJDXBerMmDzL0ABRCOKQmwvHlPKXK4elf1dtcTgNLqzg ZivCHALRQrJgb495sAGDXxkrvRGdcgLLf74tg=
Sorry if this is an FAQ I've overlooked. I'm trying to get my head around best practices wrt to rails deployment. To manage deployment/rollback of a rails app to a set of apache/passenger instances, would you create a recipe that invokes capistrano tasks, create cookbook that gems up the app, distributes and installs (how would rollbacks be handled?). I see the rails cookbook on github but it's not clear what the over all workflow is - if the rails code is housed in git, how do you specify "deploy this new revision" or "rollback to that revision"? How are db migrations handled?
thanks!
-Ian

--
Ian Kallen
blog: http://www.arachna.com/roller/spidaman
tweetz: http://twitter.com/spidaman
vox: 415.505.5208


Archive powered by MHonArc 2.6.16.

§