> > > 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. > > I use Puppet for deploying my blog. It's a WordPress distro with a bunch of plugins, etc. It was too slow. I ended up inelegantly using rsync from puppet to push out the distro instead, which was insanely fast. Even that didn't come for free as I'm not using a Puppetmaster at the moment, and paths got annoying. (I do accept that's probably my issue, however).
Anyway, my point is that Puppet needs to give you a way to deploy a tree of files, fast. If the new type mentioned above starts to give you that, so much the better: it gets tedious to push files to your version control system, ensure that your puppetmaster is up to date, and then invoke puppet on the node that you're deploying to. What's appealing about some developer-style deploy tools is that you can push exactly what you're working on to one or more nodes and test it. My experiences with Puppet suggest that it's not so convenient. My 6 years as a build and release manager tell me that it's generally a poor idea to use two application deployment tools. Hmmm. Julian J. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
