> > Running Puppet without a puppetmaster would be one reason. > > You could have a repository of your manifests that your machines check > out and run against. Cap is a poor mans way of orchestrating that > setup in lieu of something more powerful like MCollective. > > I could have asked that question in a more coherent way. I run Puppet without a puppetmaster myself. My process starts with a Rake build that invokes Puppet standalone, with all of the relevant configuration options supplied on the command line, with their paths resolved so I can check out my repo and then run 'rake puppet:run'. The original question suggested that they wanted something more complex, with a Continuous Integration-like approach to checking for changes.
Personally I wouldn't do that as you should be able to run Puppet with impunity, whenever you feel like it. To me, testing for changes suggests that someone really isn't happy about the idea :) Best Julian. -- 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.
