> > > In general you need to provide some code for puppet to apply, which isn't > the case with puppetd. Also, there'll basically be an assumption about > both: puppetd will need to run as root, it'll maintain a catalog, it needs > auth credentials, and plenty more. In contrast, puppet should always be > able to run as a normal user, should have little if any state, and probably > doesn't need certificates or any sense of membership to a network. > > > +1. I've been running the puppet command from a Rakefile all day, while I test my manifests in a VM. Also I run it against whatever file I'm editing to make sure that its syntax is correct before I do a run.
> > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com http://twitter.com/builddoctor -- You received this message because you are subscribed to the Google Groups "Puppet Developers" 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-dev?hl=en.
