> > > 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. > > For us using two different tools makes sense. For provisioning, I don't want developers doing ad-hoc stuff, so the limitations of Ansible, the non-scriptable YAML manifests, the standalone toolchain is a bonus. For app deployment, we want more control, using familiar tools Ruby/Rake etc. Cap has also figured out rails deployment - bundler/assets/etc. It is also helpful that the community focus of Ansible and Capistrano is distinct.
I guess I'm saying what you already know. :-p -- -- * 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.
