Re: rails app deployment

[Ian Kallen <spidaman.list@gmail.com>]

Oh, sweet, that's pretty much what I was imagining. Do you have plans to 
support "push" deployment (roll an app tarball, dist out to servers and 
shimmy the symlinks) ? Also (rails newbness alert) - are there race 
conditions with db migrates when you have a cluster of machines updating 
in parallel that risk fubaring the schema? I can imagine without a 
global lock asserted by the first cluster member to start a migration, 
you could get cluster members stepping on each other trying to execute 
migrations in parallel.
thanks!
-Ian

Ezra Zygmuntowicz wrote:
>     I've written chef deploy resources that handle this. The only 
> thing not implemented yet is rollback but that will be done soon.
>
> http://github.com/ezmobius/chef-deploy/tree
>
>
> Cheers-
> -Ezra
>
> On Apr 17, 2009, at 9:18 AM, Ian Kallen wrote:
>
> > 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


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