I second the notion that Ansible looks much more sane than Chef. I never liked Chef's weird "JSON and/or Ruby" mix/split, or whatever.
I also could point out that since late last year there is http://www.opscode.com/blog/2012/06/29/omnibus-chef-packaging/ which is an attempt (mostly successful) to separate Chef from any weird system stuff, this made working with chef bearable. It also hurts that there's been an open (uncared for) bug in Chef for more than three years now that means you can't use the database cookbook to create a database, or manage database users/etc. (something about the `pg` gem not being installable in the omnibus environment) I do think it's interesting that although Ansible could do what Cap is doing, you aren't using it for that. And that with Python in the stack you are using Capistrano over Fabric. Lee Hambley -- http://lee.hambley.name/ +49 (0) 170 298 5667 On 7 November 2013 16:35, Andy L <[email protected]> wrote: > Kir - we used Chef in the past, but switched to Ansible because it was > simpler. In particular - Ansible requires no server-side installs, and > pushes everything using SSH - just like Capistrano. > > Ansible is based on Python, and that has proved to be a bonus. With Chef > we got all tangled up with discrepancies between system ruby and rbenv > rubies. Ansible gave us a cleaner separation between our provisioning > tools and our apps. > > We're still using deploy scripts for our Rails app, and I think we always > will be. Docker is used to run plugins. > > Currently plugins are written by internal developers. As we get more > experience, and build a stronger plugin API, we'll open up plugin authoring > to 3rd party developers. > > > > On Thursday, November 7, 2013 12:28:30 AM UTC-8, Kir S. wrote: >> >> I’m glad to hear that. Thanks for feedback! >> >> Lately, in the company I work for (http://evilmartians.com/) we're >> trying to find some way to integrate Docker, Chef (Ansible is an option >> too) and Capistrano together. >> >> So I'm really looking forward to get more information how did you link >> these components and how to switch from deploy scripts to Docker. >> Could you tell more about it in this thread? >> >> On Thursday, November 7, 2013 6:56:52 AM UTC+4, Andy L wrote: >>> >>> I just spent my first afternoon using Capistrano V3. Cap3 is just a >>> major improvement over the previous code base. SshKit is a giant >>> improvement, the docco is way better, and the tasks are much easier to read >>> and understand. >>> >>> I've begun using Ansible for provisioning, and Docker for >>> containerization. The combination of Ansible, Docker and Capistrano V3 >>> looks like its going to be pretty fantastic. >>> >>> Cap3 is a great piece of work. Congrats to the maintainers, and 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.
