I agree. We should keep as much logic as possible in the webware tree (not in the working dirs). We _do_ need a few bits of info from the working directory in order to bootstrap the AppServer:
1. python version to execute (i.e. python2.2 vs. /usr/bin/python vs. c:\python23\python.exe).
2. path to webware installation
3. path to working dir (so that you don't have to be _in_ the working dir
to start/stop the appserver)
#1 is handled by AppServer/AppServer.bat. #2 and #3 are handled by
Launch.py. I think that all further logic and command-line parsing
(i.e. switching user/group, prompting for passwords, pid files, etc.) should
be done by code in the webware tree (not in Launch.py, but perhaps in
WebKit/Launch.py). Thoughts?
I would like to add:
4. The rest of the python path. Since I have my site hosted elsewhere, I cannot install all the libraries I use in the standard place for python libraries. So I have a hacked up Launch.py to add those folders. I would like to get all this stuff out of there, and put it on the command line or into a config file.
-ww
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
Webware-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-devel
