> > 2) Should make it easy to make global changes as you move configuration > files from development to test and production. This is something I deal > with all the time. I'll have a config file with values for directories and > host names that work for development, but need to be altered for our test > and production enviroments.
To solve this problem we use a configuration system that can builds a hierachie, where you can override parts on a host or group basis. So I have entries which defines the defaults, they gets overridden by say entries for Unix or Windows depening on the OS, which gets overridden for host specfic values. Also the base values can be parametrizied, so for example my log path looks like (RootPath)/log and in the Unix and Windows configuration I can give different values for RootPath. This scheme has proven to work very well, when the same pieces of code should run on many different systems. Gerald ------------------------------------------------------------- Gerald Richter ecos electronic communication services gmbh Internetconnect * Webserver/-design/-datenbanken * Consulting Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz E-Mail: [EMAIL PROTECTED] Voice: +49 6133 925131 WWW: http://www.ecos.de Fax: +49 6133 925152 -------------------------------------------------------------
