Is it possible to have a sub-module that has its own files and templates directories? For example, if I create a sub-module base::logrotate with a template path like this:> base/logrotate/templatesI''ve tried this, but when I try to access a template from my "base" class with a relative URL like this> template("base/logrotate/logrotate.conf")it can''t find it. Also, a little background, just in case there''s a better solution for what I want to do. I''ve split up my modules into two directories, "package" and "node". The "package" directory contains generic modules to configure packages and related groups of packages; the "node" directory contains modules to configure classes of nodes for my site. These are site-specific and heritable (for example, I have base => vserver => drupalvserver). Since I want to keep the "package" modules completely generic so I can use them from within different "node" modules (I will have "apachevserver" in future, etc.), it makes sense for site-specific files and templates to live within the "node" module hierarchy. The problem is, it''s difficult to keep track of which files/templates are associated with which "package" modules, and there are namespace collisions; e.g. the nginx package has an "nginx.conf" file, but so does the logrotate package. To get around this I''ve been naming them PACKAGE_filename, but it would be much cleaner to have sub-modules for my "node" packages, named for their respective "package" modules, that would contain their files/templates. Hope that makes sense... -- Dan Urist durist@ucar.edu 303-497-2459 -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Fri, Sep 10, 2010 at 3:02 PM, Dan Urist <durist@ucar.edu> wrote:> Is it possible to have a sub-module that has its own files and > templates directories? For example, if I create a sub-module > base::logrotate with a template path like this: > >> base/logrotate/templates > > I''ve tried this, but when I try to access a template from my "base" > class with a relative URL like this > >> template("base/logrotate/logrotate.conf")filesystem path: base/templates/logrotate/logrotate.conf works with template("base/logrotate/logrotate.conf") Does that make more sense?> > it can''t find it. > > Also, a little background, just in case there''s a better solution for > what I want to do. I''ve split up my modules into two directories, > "package" and "node". The "package" directory contains generic modules > to configure packages and related groups of packages; the "node" > directory contains modules to configure classes of nodes for my site. > These are site-specific and heritable (for example, I have base => > vserver => drupalvserver). Since I want to keep the "package" modules > completely generic so I can use them from within different "node" > modules (I will have "apachevserver" in future, etc.), it makes sense > for site-specific files and templates to live within the "node" module > hierarchy. The problem is, it''s difficult to keep track of which > files/templates are associated with which "package" modules, and there > are namespace collisions; e.g. the nginx package has an "nginx.conf" > file, but so does the logrotate package. To get around this I''ve been > naming them PACKAGE_filename, but it would be much cleaner to have > sub-modules for my "node" packages, named for their respective > "package" modules, that would contain their files/templates. > > Hope that makes sense... > -- > Dan Urist > durist@ucar.edu > 303-497-2459 > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. > >-- nigel -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Fri, 10 Sep 2010 15:13:06 -0700 Nigel Kersten <nigelk@google.com> wrote:> On Fri, Sep 10, 2010 at 3:02 PM, Dan Urist <durist@ucar.edu> wrote: > > Is it possible to have a sub-module that has its own files and > > templates directories? For example, if I create a sub-module > > base::logrotate with a template path like this: > > > >> base/logrotate/templates > > > > I''ve tried this, but when I try to access a template from my "base" > > class with a relative URL like this > > > >> template("base/logrotate/logrotate.conf") > > filesystem path: base/templates/logrotate/logrotate.conf > works with > template("base/logrotate/logrotate.conf") > > Does that make more sense?Yes! Thanks. -- Dan Urist durist@ucar.edu 303-497-2459 -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.