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

[TSVN] SVN for different setups?

From: Jan Bergquist <jb.bergquist_at_telia.com>
Date: 2004-07-26 01:59:03 CEST

I am not quite clear about the best way to set up a system for test and
production.
I have a web site running locally, for test. It has some parameters and code
snippets especially for this environment.
Most of the code, say 10 modules (A-J), are identical for test and
production.
For test vs production 2 files (say K and L) have to be slightly different.
They are rarely changed.

I need to set up my working copy for testing (A-J and KL/test).
When this is ok, I need to distribute the new versions (A-J and KL/prod) to
the 'real' web site, via FTP.

Should I set up the trunk for the 10+2 files for testing, and a branch with
the different versions of the 2 files?

Is it better to have one working copy, and do a switch when testing is
ready - or should I have 2 different working copies (one for testing
locally, and one for distribution to real site)?

(It could be a similar problem if you have e.g. if one module varies for
different customers you are working for. I found 'Vendor branches' in the
svn docs, but nothing about 'Customer branches').
Is there a 'best practice' way to handle these things with svn?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Jul 26 03:08:21 2004

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.