Re: Website development

[Derek R. Price]

Chris Chambers wrote:

> > -----Original Message-----
> > From: address@hidden [mailto:address@hidden Behalf Of
> > Derek R. Price
> >
> > Chris Chambers wrote:
> >
> > > I've been staring at this ugly fact for a while... if it's at
> > all possible
> > > to do the gruntwork required to create a sandbox for each developer, I'd
> > > recommend going that route. Otherwise, I recommend a locking model.
> >
> > 'cvs co projectname'?
>
>

> Hey I'd love to hear more about what you're thinking here!
>
> It sounded to me like we had multiple developers sharing one CVS account or
> otherwise editing a CVS module checked out to one place on the server, say
> "/home/http/cgi-bin".
>
> My point was, unless we can set up a "cgi-bin" for each developer, CVS won't
> work well in this environment; developer A and B can try to edit the same
> piece of code and overwrite each other's changes. It was specified in the
> post that setting up different webservers for each developer wasn't easy.

Well, first of all, you could put each developer's individual workspace in
subdirectories under the _same_ cgi-bin.  That should encourage your developers
to make things easily reconfigurable anyhow.

Another possibility introduces an extra step for everybody, but basically
allows concurrent development.  In that model, developers work in their own
workspaces then copy files that need testing into the public area or check them
in and have a checkin hook exporting the data into the test area.  Then you
only have to worry about who's _testing_ a file at the same time as you and not
who's _editing_ it.

Derek

--
Derek Price                      CVS Solutions Architect ( http://CVSHome.org )
mailto:address@hidden     OpenAvenue ( http://OpenAvenue.com )
--
When you find yourself getting irritated with someone, try to remember
that all men are brothers...  a noogie or an Indian burn should do the
trick.