[plug] Source control for webapplications

[rod]

in situations like that I would have 2 little scripts (pull,push)
that "do the right thing" at pulling the latest data/code down and
pusing it back up again.

everyone has to have the discipline to 'pull' before doing work, then
'push' when happy with the work... and any manner of 'nasties' can be
hidden in the pull and push scripts ;P


I do have some suggestions tho....

1) I would not have the live database as the 'master schema' ... I would
have some scripts that created the correct schema, and these would live
in the revision control system - this means you would not be using the
live database at all on devel machines, which would be correct imho.

2) do use Arch or subversion or CVS or any revision control system ...
having multiple people work directly on live code is a disaster waiting
to happen... I cant imagine working without the safety of revision
control.. it makes me shudder ;)

3) make the live site a 'checked out' or 'pull'ed version... this way
you can decide when the new code goes live by only updating it when the
developers have fully tested their new code. if you have (as suggested)
moved all the database creation/population to scripts in cvs (where they
belong!) you then deploy the new site on a test/devel machine easily.