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 _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
