Hi guys,

As Peter points out, this thread is old. Sorry I dropped the ball, I
plan on integrating feedback and getting this updated this weekend.

--Paul

On Wed, Sep 16, 2009 at 6:40 AM, Peter Meier <peter.me...@immerda.ch> wrote:
>
> Hi
>
> so I took again a look a this rather old thread, as I tried to implement
> things as I thought I have understood them.
>
>>>> good idea! Currently I have all site specific stuff in one big module,
>>>> but like that I might be able to organize it again in modules per each
>>>> site specific module adaptions. Question: Is autoloading looking in
>>>> both module directories? so if it's not found in the module in one
>>>> module directory it's still looking in the other one? I assume so, but
>>>> as I haven't used it yet I better ask... ;)
>>>
>>> modulepath option must be set in your puppet.conf file.
>>
>> yeah, that for sure. But so I assume it looks for ssh::client in every
>> ssh module it can find in the different modulepaths.
>
> After this discussion I thought that modules can be scattered amongst
> the various module paths. But this doesn't seem to be the case. At least
> my experience shows that puppet simply respects the classes of a module
> it founds in the first location, all the classes in a second location
> get ignored.
>
> So the best practices would be to have 2 module paths, one with the
> public modules and one module path with the site-specific module -
> extensions, prefixed with site? so something like:
>
> modules/public/apache <- public apache module
> modules/site/site-apache <- site specific implementations of apache
>
> To throw up the question:
>
> Wouldn't it be nicer if puppet would collect a module's classes from all
> module pathes? It would at least make my site specific module changes
> look a bit nicer and I still wouldn't have to mix these. However I see
> all the problems coming up with this solution. I'm just curious what
> other people think.
>
> cheers pete
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
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+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to