Re: [Blosxom-devel] Allowing external configuration with blosxom

[Gavin C. <ga...@op...>]

On Wed, Aug 29, 2007 at 08:48:38AM +0200, Gerfried Fuchs wrote:
> > > By the way, regarding blosxom configuration through external files, I  
> > > wonder if we shouldn't improve the "config" or "prefs" plugin to make  
> > > sure they run early (in start ?), rather than risking confusing users  
> > > with another set of configuration files ?
> > 
> > You've still got a bootstrap problem though - you've got to define your
> > plugin config variables in order to find your plugins in the first place.
> 
>  But the $plugin_dir is specified already through blosxom.conf - the
> plugins are found then.  

Yes, that's what I'm saying - you can do lots of stuff through the config
or prefs plugins, but you can't configure the settings required to find 
those plugins. So if you want to configure _those_ settings outside of
blosxom.cgi, as I do (for upgradability), then you've motivated your 
separate blosxom.conf.

> I really prefer the config plugin approach of
> setting plugin specific variables, I don't think that having files in
> the etc config directory is needed for that. Besides that plugin
> specific variables can _also_ be set through that blosxom.conf.

Can you explain how that would work? I'm not familiar with that approach.

Say I want to use the 'atomfeed' plugin, for instance, which has two 
mandatory config variables, $default_author and $feed_yr. How would you
set those (not doing it in the plugin itself, of course)?

Cheers,
Gavin