Hi, > IIRC this was briefly mentioned in the past, but I'd like to hear from > the Apache team if there is still interest/consideration in providing > a programmatic module enable/disable interface (CLI). > > In Debian there is a2enmod and a2dismod which are used to enable/ > disable > available Apache modules. > > As we start to include more and more optional modules which drop their > optional but disabled-oob config into samples-conf.d, it might be nice > to provide a tool for users to selectively enable some of them by > name. > > The workaround is of course to simply 'cp samples-conf.d/foo.conf > conf.d/' > so it is not a vital tool, but would be nice to have a stable > interface/CLI for scripting instead of requiring everyone to bake in > the absolute path to the samples and conf dirs into their scripts.
Well, to put another suggestion into the pot... Gentoo place the sample module configurations into conf.d, and then use the defines system built into Apache to select which modules to actually use. This means all the modules are always in /etc/apache2/modules.d, and then an IfDefine within the module is used to determine which modules to use. You then configure the module configs to be included by editing the / etc/conf.d/apache file with the list of -D MODULE elements to include on the command line. I would have thought (but could be wrong) that this solution might work nicer with SMF, because we could use the SMF properties interface to configure the list of 'defined' modules. This wouldn't require any additional command line tools (we could the existing SMF and Apache infrastructure), but would require some modifications to the module config files already included to ensure the necessary IfDefine's were included properly. MC -- Martin 'MC' Brown, mc at mcslp.com and mc at mysql.com Technical Writer, Database Group, Sun Microsystems Everything MCslp: http://planet.mcslp.com
