hello, > >>> puppet.conf contains (in addition to the standard stuff): > >>> > >>> [staging] > >>> modulepath = > /etc/puppet-staging/modules:/etc/puppet-staging/services > >>> manifest = /etc/puppet-staging/manifests/site.pp > >>> > >>> [development] > >>> modulepath = > >>> /etc/puppet-development/modules:/etc/puppet-development/services > >>> manifest = /etc/puppet-development/manifests/site.pp
> I'm not following Matt. If you have multiple base directories, > /etc/puppet, etc/puppet-development and so on, how do you serve up > content from all three locations at once with a single puppet master? > I know there's environments, but are you saying the puppet.conf in > /etc/puppet refers to module and manifest dirs that are outside > /etc/puppet in /etc/puppet-development? /etc/puppet isn't special in any way, it's just a directory. Look at the sample config quoted above, it tells the master a different modulepath and manifest for each environment. So machines in staging and machines in development gets served by the master based on this config from other directories, doesn't matter where they are. When a development machines does: include apache or source => puppet:///apache/httpd.conf it will fetch the code for the apache class from /etc/puppet-development/modules/apache/manifests/init.pp and the file from /etc/puppet-development/modules/apache/files/httpd.conf -- R.I.Pienaar -- 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.
