On Friday 07 December 2001 02:45 pm, Tavis Rudd wrote: > But Geoff suggested that it might be better to require an explicit > arg to the start script to make damn sure it doesn't get them from > the wrong place. �I don't think it's that likely. Nonetheless the > launcher script should loudly declare where it is getting its > settings from.
We can mitigate that by printing the path info upon launching, as you've implied and advertising it in the admin servlets. > Personally I like your suggestion of using an env var. �If we went > with a python package to contain the configs then you could use > PYTHONPATH to locate them, unless WEBWAREPATH was set. �... something > like that. > > The big question though is are we talking about 'WebKit' configs or > 'Webware' configs??? �There's a big distinction there. �'Webware' � > configs would allow us to deal with the settings for all Webware > components in one place. �I don't think the local settings for > MiddleKit, UserKit, PieInTheSkyKit, etc. should be sitting in the > WebKitConfigs directory. �Do you? Good point, but I wouldn't mind seeing all Python projects at least use the same path conventions for configs even if they're not Webware. Is CONFIGPATH too generic? Maybe PYCONFIGPATH? Well, it's back to contracting for me. Talk to you guys later. :-) -Chuck _______________________________________________ Webware-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-devel
