Puppet

and what about defining traditional fileserver locations?

http://projects.puppetlabs.com/projects/puppet/wiki/File_Serving_Configuration

Somehowe I think this will collidate.

I can’t say that I’ve thought of a perfect solution yet, and perhaps I’m missing your point.

But my situation is that I have a list of hosts (or, rather, subnets) which I want to allow access to every module. It’s getting to be a bit of a pain to have to add more or less the same directive, except for the module name, to fileserver.conf every time I add a module.

I’d be just as happy to have a config option to totally ignore fileserver.conf, and just specify a base module path and a list of allowed hosts/subnets.

For the time being, I added a script called by a Makefile that, prior to every commit (I keep puppet configs in SVN), runs through the modules/ directory and generates fileserver.conf – with identical stanzas for each module, just with the correct name and the module name plugged in to create the correct path.

If there was some way to achieve this out-of-the-box it would be much simpler – perhaps it would be better with some reserved word, like an [—ALL—] module with some placeholder in the path, that would provide configuration for any module not explicitly configured.

I’m nearly positive the following works fine:

[modules]
    192.168.0.*
    10.0.1.*
    10.0.2.*

Doesn’t it?