Setting up Vault repository for project lifecycle

Branestawm · Post by **Branestawm** » Wed Jul 02, 2008 4:44 am

Hello. I am setting up a new installation of Vault to use with web application development using VS2003 & VS2005. What is the normal / best practice for configuring the repository to reflect the development, test and live environments? How is migration from dev to test or test to live performed? Any suggestions gratefully received, I have not used this type of source code control before. Many thanks.

lbauer · Post by **lbauer** » Wed Jul 02, 2008 6:32 am

One way to do this is to use branching. For instance the trunk could be the production or live site files. Then you could create branches for development and test. To migrate changes, use Vault's Merge Branches wizards.

You could also use Shadow Folders to push files to the live site from the Production trunk. A shadow folder is a directory on the local LAN that is synchronized with the latest version of the folder in the repository.

More info on branching:

http://www.ericsink.com/scm/scm_branches.html
http://support.sourcegear.com/viewtopic.php?t=193

Branestawm · Post by **Branestawm** » Wed Jul 02, 2008 7:25 am

Hi Linda, thanks for this response, this info is very helpful. Is the method you describe common practice? Or is it more usual to use the source control at development level only and to push the apps through to test and live outside source control? Thanks.

lbauer · Post by **lbauer** » Thu Jul 03, 2008 6:30 am

We use the type of branching described, but our end product is different than yours. We have a product that is installed rather than a web site.

So you could just do development under source control and check-in "approved" files after testing, and populate the live webapp with a shadow folder functionality or by doing a get with the commandline client.