> > Example of what capistrano can do best: > > A. Deploy your puppet manifests to your puppet server. > B. Deploy your web content out of svn onto your web server. > > They're two distinct areas of 'deployment'. Puppet is more like, systems > deployment, cap is app or content deployment in my eyes.
Yes, I want to change that observation. For instance, there are pretty good examples of deploying rails apps with Puppet, but it's not well shared. We similarly need to create examples for other types of applications. The Source Control Management type that Bruce is working on (should be available soon?) covers your case B and should be tremendously helpful there. I believe the two should not necessarily be distinct and it's very good to have them in the same model so you can have dependencies between them. This all goes down the line of doing minimal kickstart + Puppet. I don't want Puppet to be like kickstart and reach a arbitrary deployment line and stop -- it is too interesting for that. --Michael -- You received this message because you are subscribed to the Google Groups "Puppet Users" 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/puppet-users?hl=en.
