2009/1/22 Gerhardus Geldenhuis <[email protected]>: > > Hi > vs might be a bit of a controversial term. I am really interested in > peoples opinions about the overlapping or symbiotic relationship > between capistrano and puppet. If you are using both tools, could you > expand on the relationship between the tools in your usage of them? > > I have some thoughts on the subject but have on purpose not shared the > immediately as I feel that would be a leading question. :-) >
I view them as completely different tools for different tasks. Puppet is a tool for configuring the server that my app runs on, installing and configuring linux networking and user accounts, apache, mysql and monitoring tools. Capistrano is a tool for deploying my application to one or more servers and scripting shell interactions with that application's environment. The only grey area is on direct project dependencies, my application being a python app do I use setuptools (via capistrano) to install the dependencies or do I use Puppet and debian's packaged version of those same dependencies. But that's another holy war in itself :-) To put it another way you could say that Puppet is for sysadmins, Capistrano is for release managers. --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
