RE: Use existing directory as repository
From: Giulio Troccoli <Giulio.Troccoli_at_uk.linedata.com>
Date: Fri, 20 Aug 2010 10:48:35 +0100
Linedata Limited
________________________________
From: Tim Asplin [mailto:tim.asplin_at_gmail.com]
Hello,
I have read through the manual, and looked at FAQ. But did not seam to find the answer.
We have a web site, and directory structure to support it, what we want is to use subversion to now manage it. So want to use the existing structure of directories and files as the repository to check out files from, while also having the files running on the development web site so we can still use the website.
In the manual it show you how to create a repository and how to import a existing folder into it, and in the FAQ how to create a repository and use files as working set.
What we want to do is to turn the existing structure into the repository, is this possible, if so how.
Were are running on windows.
Thanks
Tim
The repository is where you store all your files and history. The working copy is a copy of the repository, or part of it, where you can do your work.
So in your case you do want to use the existing structure to populate the repository, with the import facility as explained in the book, but the repository will be somewhere else, somewhere accessible by all your developers.
If you decided to use the recommended trunk/branches/tags structure you would have your live website as a working copy (or maybe as an export) of a specific tag and use branches and trunk for development, i.e. your developers would create a working copy out of trunk or a branch and commit to it. Then, when your code passes the test, probably in a staging place, you can create a new tag and switch the live site to it.
Hope this helps. I don't do website development (although I might start soon), this is what I gathered by reading the ML through the years.
Giulio
P.S. Please post in text-format only
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.