[chef] Re: Rails deployment scenarios - capistrano vs application cookbook

[Max Gorbul < >]

We have chef-client running every 30 minutes. But sometimes deployment need to be executed earlier then in 30 minutes. So we use chef/capistrano deployment.

basically cap deploy:setup and some configuration which depends on the infrastructure (database, redis etc.) are deployed and managed by chef. The code itself is deployed from git repo by capistrano. There is a deployer host which holds all the projects and user who is able to run cap deploy form there in order to deploy to prod env (regular developers do not have access to prod).

There is a monitor running which checks repo changes or CI successful builds every minute and triggers deployment job as soon as one of those changes happens.

--max

On Mon, Feb 13, 2012 at 9:30 AM, Ryan Richards < "> > wrote:

Hello chefs:

Ive been using chef for some time but have yet to use the application cookbook and the deployment resource. Most of the applications i work with are ruby on rails. Traditionally capistrano is the deployment tool of choice but it seems that if you already use chef for managing infrastructure, the 'application' cookbook would be good to have in the toolbox.

Im currently working on a project where we use capistrano and the opscode platform. We are starting to cross the boundaries between typical development activities and actions that could benefit from some of the chef 'intelligence'. Are there many rails apps that use application and chef-deploy to replace capistrano? (i believe you need both resources?)

thanks for any insight
Ryan