Re: Ideal Subversion Setup

On Dec 16, 2009, at 10:00, David Burleson wrote:

> I have been using subversion with TortoiseSVN for a couple of years now. I work in a team of 3 web developers on multiple websites. Im starting to wonder if the way we use subversion and version control is the correct way. So, I have posted to ask advice on the best way to use Subversion in a web development team with multiple projects.
>
> We currently each have our own development area on a local web server for each project. We also each have our own SVNcheckout of each project.

Sounds good to me!

> Once we have checked out/updated our 'repo' we drag the contents over to our development area to work. Once we are finished working, we drag the files back over to our 'repo' and commit it.

Where you say "repo" you actually mean "working copy" (or "checkout"); the "repo" or repository is what you check out from and commit to, and there is only one of them, on your Subversion server.

> I have a feeling that the better process is to make your development area the SVNcheckout.

I would completely agree with that. You're making a lot of unnecessary error-prone work for yourselves by manually moving files around.

> My only problems is how subversion and TortoiseSVN handle symlinks and file/dir permissions. We have a couple of symlinks for folders like 'images' so we don't have to duplicate the directories on the webserver and some folders which we upload files too have 777 permissions and what not. I don't know if subversion or TortoiseSVN will pass these own and treat the symlink as a symlink and not a folder, and pass the permission into the 'repo' too.

Subversion handles symlinks just fine, but Windows does not. (There is no such thing as a symlink on Windows.) So I'm not clear on how you're using symlinks on Windows at all, unless you're using cygwin. In which case you should use a cygwin Subversion client, not a Windows Subversion client like TortoiseSVN.

Subversion repositories do not store or retain file or directory permissions or ownership. The only exception is the execute bit on files, which can be preserved by setting the svn:executable property of that file to any value (which Subversion automatically does if you add a file that's executable).
Received on 2009-12-17 04:34:14 CET