I just tried using capistrano-unicorn and capistrano-nginx-unicorn gems
I think they both need to be fixed up to use blocks in their default values, (ie use lazy evaluation) so that they work better with multistage configs or out of order recipe loading. It led to some confusing bugs. Also they weren't quite right to fit our needs, It might be easier just to copy the tasks they define and copy them to suit your needs. The capistrano-nginx-unicorn gem uses a "template" pattern using erb on config files which would be a lot more like chef I liked that pattern. it also has a more thoroughly setup init scripts for unicorn. (makes an init.d script ) If you already have chef running you might like to set things up as "things I need root use chef", "things at deployment time use capistrano". for me currently things that need root happen in deploy:setup and other stuff happens in deploy. In any event I don't think either are drop in solutions, I was forced to learn and tweak what they were doing to make them work for my situation. They try but they are not quite generic enough. --fess On Feb 4, 2013, at 11:15 AM, Boris Quiroz wrote: > Well, that's more or less the question. I've an environment with unicorn and > nginx, and our old deployment process was using Chef (manually running > chef-client on every machine and then restart unicorn process). Right now I'm > migrating that deployment process to Capistrano and I wanted to know, > according to the experience of the people on this group, what is the best way > to manage unicorn, using Capistrano or continue managing using Chef? > > I've been reading about this gem > https://github.com/sosedoff/capistrano-unicorn, I've done some tests on > staging environment, but I'm not 100% sure if that is the best option so any > comment and/or advice is welcome! > > Thanks. > > -- > -- > * You received this message because you are subscribed to the Google Groups > "Capistrano" group. > * To post to this group, send email to [email protected] > * To unsubscribe from this group, send email to > [email protected] For more options, visit this group at > http://groups.google.com/group/capistrano?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Capistrano" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > -- -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to [email protected] * To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano?hl=en --- You received this message because you are subscribed to the Google Groups "Capistrano" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
