Webware for Python

At 10:39 AM 10/27/2001 +0200, Georg Balmer wrote:
>I have 2 basic questions
>
>--[1]--------------------------------------------
>
>How do you layout the directory structure ?
[snip]
>or case B:
>
>someDirectory/
>     Webware/
>         WebKit/
>         ...
>
>someOtherDirectory/
>     appOne/
>         pages/
>         lib/

Case B. Mingling your projects with Webware is a bad idea. It makes it 
harder to upgrade Webware and confuses people into thinking they have to 
modify Webware to make Webware apps.

One notable exception is when you bake your own plug-ins. Those can be 
convenient to drop into Webware/ because then they get picked up 
automatically. However, there are 2 settings related to this in 
WebKit/Configs/AppServer.config which allows you to put your plug-ins 
outside of Webware.

Just for clarification: If you are building a Webware site, you are 
probably NOT creating a plug-in.


>--[2]--------------------------------------------
>
>Where does the locaction tag of the
>appache configuration file point at
>(using mod_webkit) ?

Mine is set to:
<Location /webkit>

Which means that when I want to access WebKit apps on my system, the URL is:
http://localhost/webkit/somecontext

or even just:
http://localhost/webkit/

to see the default context.

When I use the OneShot.cgi adapter for development, my URL is:
http://localhost/OneShot.cgi/

So for mod_webkit, the Location is just a way to partition off a URL space. 
Presumably you could then use mod_rewrite if you have a Webware-only site 
and you wanted to get rid of this in your public URLs. I haven't done that 
yet, but I believe others have and I will be soon.


-Chuck

At 04:35 AM 10/27/01 -0700, Chuck Esterbrook wrote:
>At 10:39 AM 10/27/2001 +0200, Georg Balmer wrote:
>>I have 2 basic questions
>>
>>--[1]--------------------------------------------
>>
>>How do you layout the directory structure ?
>[snip]
>>or case B:
>>
>>someDirectory/
>>     Webware/
>>         WebKit/
>>         ...
>>
>>someOtherDirectory/
>>     appOne/
>>         pages/
>>         lib/
>
>Case B. Mingling your projects with Webware is a bad idea. It makes it 
>harder to upgrade Webware and confuses people into thinking they have to 
>modify Webware to make Webware apps.

I agree.  And I recommend using the MakeAppWorkDir.py script that can be 
found in the Webware/bin directory to create a separate working directory, 
complete with its own config files, etc.  That way, you don't have to 
modify the Webware directory at all.

Then you can add your own library directories into the directory that you 
created with MakeAppWorkDir.py.  So my directory structure looks like this:

/Webware
     /WebKit
     ...

/MyWebSite
     /Cache
     /Configs
     /Contexts - I added this directory
         /SomeContext
         /SomeOtherContext
     /ErrorMsgs
     /Lib - I added this directory
     /Logs
     /Sessions
     /Static - I added this directory for static content to be served 
directly by Apache
     AppServer.bat
     Launch.py
     ...

 From my servlets I can import Python modules out of Lib using for example:

from Lib.SitePage import SitePage


--

- Geoff Talvola
   gtalvola@...