Thanks Chuck
It seems to be working fine with the few developers that we have.
Obviously though, on larger projects (say 10/15 developers +) this will
become prohibitive due to the disk space and time consumed in setting up
all the separate copies.
I'd be interested in hearing about other possible solutions (if any occur
to you) so that when our company and team grows (positive thinking here!),
there's a way I can attack the development environment question.
Cheers,
Mark
-----Original Message-----
From: Chuck Esterbrook [mailto:[EMAIL PROTECTED]]
Sent: 26 July 2001 03:29
To: Geoff Talvola; Mark Gebhardt; Webware discuss list
Subject: Re: [Webware-discuss] Webware/Webkit and development
environments
At 10:44 AM 7/23/2001 -0400, Geoff Talvola wrote:
>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.
These are both good suggestions and should probably be the way Mark goes,
but I'm also wondering if Webware CVS would solve this. Earlier versions
of
Webware added each context to sys.path which then lead this other problem.
This was fixed (by Geoff) in CVS.
I see from a later message, Mark already created the separate copies.
You're probably best off leaving that configuration as it guarantees
separate sandboxes.
-Chuck
smime.p7s
