[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Want to set up SVN for a web app

From: Andy Levy <andy.levy_at_gmail.com>
Date: Wed, 1 Apr 2009 13:52:35 -0400

On Wed, Apr 1, 2009 at 10:44, Theodore H. Smith <delete_at_elfdata.com> wrote:
> Hi Guilio,
> Here is one question that might help me and be easier for the
> subversion people to answer.
> OK let's assume I know what VC systems do in general. Maybe not the
> specific commands used by each system, but the general idea.
> Now, when you are developing a desktop app, you normally care about
> code in two places. One, on your computer, and two on a central server
> shared by your co-workers.
> That makes for a simple model. You test the app locally, and when you
> are happy, you try to merge your code back into the central server. OK
> great.
> But what about a web app? When the testing is done on the server? In
> this case, there is code in THREE locations.
> One, on your hard disk where you are editing the files. Two, on the
> server for testing. And three, on another location on the server, for
> live use (production).
> How does SVN fit into that? What is the "Best practice" (for someone
> who highly favours simplicity and ease of use) for this kind of set up?

Same way you would for the 2-copy model, just with an extra copy. Work
locally, commit. Check out to or update the test server. When
validated, check out to or update production. The repository doesn't
know or care what you do with the copy you check out, it only cares
about commits..

> I still can't get my head around how a VC, would be set up for a web
> app.
> I appreciate my original question maybe wasn't so good. And I
> appreciate that you said you don't personally use SVN for web apps.
> Perhaps this question will get a better answer :)

90% of my SVN usage is for web apps and document management. I don't
just have 3 copies (local, test, production) to manage, I have (for
one of my web apps):
* Local (my desktop, for development/early unit testing)
* 2 instances for developer testing
* 8 instances for integration/acceptance testing
* 2 instances for production
* 110 instances for training (I might be off by 10% or so there, but it's close)

Why I have so many instances of a single app is a long, twisted story.
The point to take away is: it scales. Quite nicely.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-01 19:53:41 CEST

This is an archived mail posted to the Subversion Users mailing list.