Is there a reason why there is one big configuration file? Why not split the cfg file in 2, 1 in the bin directory (as it was in the latest production release) and 1 in the the lib directory (as it is now).

• The lib config file would contain the general (system wide) setup and the defaults.
• The bin config file would contain
  • the location of the lib directory (now it is a "fixed" location)
  • overrides for the defaults

Why the sepeartion?

• In case you have several twiki environments on 1 machine and most of them use the same defaults, but there are some minor configuration differences
• Being more free, without changing code, to place the lib folder anywhere you want (or able to)
• In case of an update of the twiki backend with some major updates in the config file, it only has to be done at one place. For some of the updates you might want to update the bin config file, but that's not always required.

-- HansDonner - 19 Aug 2001

TopicClassification:

FeatureEnhancementRequest