RE: [Webware-discuss] Webware/Webkit and development environments

[Mark G. <ma...@sa...>]

Thanks Geoff

That seems to have worked, and, while its obviously not a great solution for
a project with loads of developers, we have less than five, so it should
suit us just fine.

For the benefit of the archive, here's what I had to do to enable multiple
developers to use a single cvs repository and each be able to access their
own checked-out development library through Webware/WebKit. (all on RedHat
Linux 7.0):

1) for each developer, install Webware in a separate directory (eg:
/usr/local/WebwareMark, /usr/local/WebwareGraeme ...)

2) alter the permissions so that the developer can access the directory (in
my case, I just did a chgrp -R <groupname> * in each Webware install dir.

3) cd /usr/local/Webware<Name>/WebKit/Configs

4) pico Application.config
 - add a context pointing to this developer's working area (eg
/home/mark/Working)

5) pico AppServer.config
 - change the port number to a unique one so that they don't all clash (I
used 8086, 8087, 8088 ...)

6) ensure that the developer's pythonpath points only to their own working
directory (this is key, as inclusion of multiple paths that point to the
same filenames was what caused the original problem)

7) in /var/www/cgi-bin (or wherever your cgi script directory is) make
multiple copies of WebKit.cgi, one per developer (ie WebKitMark.cgi ...) and
ensure that the WebwareDir in each .cgi file points to the relevant install
directory (i.e. /usr/local/WebwareMark).

8) Now browse to http::/<hostname>/cgi-bin/Webware<Name>.cgi/ and you should
have your very own installation of webware, from which you can access only
your own development code (and for which you can stop and start the
AppServer to your heart's content.

Whew

Thanks again for the help

Mark



-----Original Message-----
From: web...@li...
[mailto:web...@li...]On Behalf Of Geoff
Talvola
Sent: 23 July 2001 04:45
To: Mark Gebhardt; Webware discuss list
Subject: Re: [Webware-discuss] Webware/Webkit and development
environments


At 10:28 AM 7/23/01 -0400, Mark Gebhardt wrote:
>Hi All
>
>We have recently had a look at Webware and selected it as our
>development
>platform for an e-commerce application we are developing.

Great choice :-)

>As we expand the team that is working on the application, I am running
>into one or two hassles and though that someone else might have had
>similar experiences and be able to offer some advice.
>
>We have our code repository stored in CVS and individual developers
>check
>out the entire site and work on their sections. In order to test their
>applications, I have set up Webware with a context pointing to each
>developer's working directory.
>
>The problem arises in that each working directory contains a number of
>packages and the same packages exist in each developer's directory and
>this seems to confuse Webware, as it is accessing packages out of other
>developer's directories. Basically, sys.path gets populated with
>multiple
>directories containing the same package and this causes a problem
>
>I have tried using OneShot.cgi, but this often seems to result in errors
>where WebKit.cgi works perfectly.
>
>Can anyone offer any advice on this?
>
>Thanks
>Mark

My advise would be to just set up totally separate copies of the app server
for each developer to avoid these problems.  Contexts are not isolated
enough from one another to allow what you're trying to do.

You can look into the "MakeAppWorkDir.py" stuff that Robin Dunn checked
into CVS recently.  Its purpose is to set up independent working
directories that are isolated from one another, but share common Webware
code from a central location.  But there's also nothing wrong with making a
full copy of the entire Webware tree for each developer.


--

- Geoff Talvola
   gtalvola@NameConnector.com

_______________________________________________
Webware-discuss mailing list
Web...@li...
http://lists.sourceforge.net/lists/listinfo/webware-discuss