Yeah, but what about deprec? That is using Capistrano to setup a lot  
of the things that Puppet is meant for.

I see them more as tools that have the capability of playing together  
nicely if you take a position on how you will use them in your  
network. I currently use Puppet for the things that we have as  
assumptions for our applications (assume that Java is installed, that  
the smtp server is here, etc.) and Capistrano for managing the  
specifics of our application. In practice, that means that Capistrano  
is used for rolling out new versions of our app, and Puppet is used  
for everything else.

I use Capistrano to bootstrap my new machines to the point where they  
are puppet nodes. Once puppet is up and running, the puppet manifest  
takes care of installing whatever else is needed. Then Capistrano is  
used by our dev team to roll out the app.

-dave

On Jan 22, 2009, at 2:03 PM, Jonathan Share wrote:

>
> 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.
>
> >

-dave

--
David Grandinetti
We Go To 12
+1 315.569.2594
[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
-~----------~----~----~----~------~----~------~--~---

Reply via email to