[pmwiki-users] sample config - not so clear
Patrick R. Michaud
pmichaud at pobox.com
Sun Jan 30 16:55:28 CST 2005
On Sun, Jan 30, 2005 at 11:26:06PM +0100, Patrick Ogay wrote:
> >.... or provide a farm-sample-config.php file. More work for PM but
> less to confuse a new admin.
>
> For me it's not so evident:, too.
> I make now the most configuration global, that means in farmconfig. php.
> In the single wikis I just assign the logo and particular settings.
> I think that "main" config.php (in the same path as farmconfig.php) ist
> also global for all other wikis.
No, the farm's config.php is not global for other wikis -- only the
farmconfig.php is global across wikis.
> my wish:
> For testing I would be practical to make the settings in a pmwiki-page,
> like [[Main/Settings]] (similar to twiki)
I've thought about this many times. But I keep coming back to a variety
of issues with placing settings in a wiki page:
(1) it's hard to do extensibly (e.g., for cookbook scripts)
(2) many configuration settings such as custom markups don't lend
themselves to simple on/off or text-field values
(3) it adds processing overhead to page requests to parse the
settings the wiki page (although such pages could possibly
be preprocessed and the results cached)
(4) we'd likely need per-group [[Settings]] pages (and per-page
settings seems difficult)
(5) ultimately it adds even *more* complexity to site configuration
(especially if we have to worry about interactions between
the wiki-page settings and various config.php scripts)
In the final analysis, I've always come to the conclusion that it's
better for admins to start out by learning to configure things in
config.php and friends than it would be to add complexity by adding
a limited UI-based interface that would eventually be outgrown.
:-) :-) Plus my (now dated) experience with TWiki installation and
configuration keeps me from seriously considering it as a prototype
for "easy to configure". :-) :-)
Pm
More information about the pmwiki-users
mailing list