At 09:02 AM 7/26/2001 +0200, Mark Gebhardt wrote:
>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
If I had a project with 15 developers, I would get each developer to
install Apache and their own copy of Webware and the application code on
their own personal development machine. I wouldn't try to set up an
environment where 15 developers are all developing on a single development
web server machine, which I think is what you're doing.
Actually, I wouldn't make each developer do all the setup themselves -- I'd
use a revision control system like CVS (or better yet, Perforce) to make it
easy for any developer to check out a consistent copy of Apache, Python,
the 3rd-party libraries being used, Webware, etc. with a single
command. The more developers, the more sense it makes to automate the
setup of the development environment.
Then I would also set up nightly "builds" of the application so that every
night a fresh new copy of the application is installed on a test server
somewhere. This would also be driven off CVS or Perforce. And I would
write a "deploy" script which can take a particular nightly build and
deploy it on the "real" web server.
I've done some of this stuff myself -- the nightly build and deploy script
-- so if you need further information on how I set that up I'd be happy to
share.
- Geoff
_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/webware-discuss
