On Mon, Oct 25, 2010 at 9:52 AM, Patrick <kc7...@gmail.com> wrote: > > On Oct 25, 2010, at 8:12 AM, Alaric wrote: > > > Hi folks, > > > > This may be a totally dumb question, but hey.. sometimes I'm dumb.... > > > > recently I've been rocking template's like a crazy person.. and I'm > wondering, is there any reason why I shouldn't use templates for *all* files > I want to manage, rather then have some files defined under files directory > some in templates, and some content defined in the manifest itself.. I'm > thinking that as I train our team to use puppet, having two possible source > of content to look at would be easier then three. Are there any pro/cons to > using templates exclusively? > > Sure, it's slower. That being said, I'm not sure if the performance > difference will be big enough it matter. > > Also, in case it wasn't clear, there are fundamental differences between file/template and a source specified file like puppet:///foo/bar
The former will: * be shipped as part of the catalog * always be shipped to the client in the catalog regardless of client state * can be applied offline The latter will: * not be shipped as part of the catalog * fetched at catalog application time, but only if the client requires it * cannot be applied offline -- Nigel Kersten Product Manager, Puppet Labs http://www.puppetlabs.com Twitter: @nigelkersten -- 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.
