-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Jan 26, 2005, at 10:42 AM, Ryan Schmidt wrote:
> It's clear that Subversion, like CVS, is built around the "work on the
> local machine" mentality, and that this works well for projects with
> far-flung developers where the end result is a compiled executable.
> But as I'll try to explain, this doesn't work so well for projects
> which are PHP/MySQL web sites with a team of developers working in one
> office building. The fact that it's a web site means the working copy
> needs to be on a web server, and the fact that the development team is
> physically located together means a central server is the right model.
>
> I think this post finally describes the situation that JC finds
> himself faced with (and me too):
snip...
> The problematic situation is the fact that the working copy has
> (because that's how web-based projects with large databases work best)
Having developed and managed development of just these sorts of web
applications, I would completely disagree. Ideal situation BY FAR
is to have a web server PER DEVELOPER, with documents and applications
in WCs PER DEVELOPER. DB per developer is ideal as well, but
is sometimes too difficult to implement mid project.
But, you can certainly develop any way you choose.
What is the difficulty of having a local WC on each developers box, and
having them edit and move files (either way!),
and commit when they're finished?
If you have any sort of shared WC, then you're going to run into all
sorts of (potential) development conflicts where
people can (and will?) lose work.
- --
- -- Tom Mornini
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
iD8DBQFB9+q2zaKkuvKwKvcRAuBtAKCWol9t86V2mXeF1F9REZFqdwAQwQCeIb8t
+MZ2eVPOB9tGhZI5i32Wu20=
=A7bv
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 26 20:14:03 2005