RE: Website development

[Chris Chambers]

> > 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.

It sounds like you're still thinking about the possibility of separate
workspaces for each developer (under cgi-bin or wherever)... I thought that
was specifically what the poster couldn't do.

If it's at all possible to do that, it's the way to go. Otherwise, CVS isn't
the right tool for you, and you should switch to an exclusive-lock model.

-Chris Chambers