is Visual SVN Server generally viewed as a trustworthy SVN server? I went to Wikipedia and didn't see any item for VisualSVN Server under Visual SVN so I added a line there... but there seems to be no mentioning of it otherwise.
+6
A:
My company has been using it. As far as I can tell, it's just a custom distribution of SVN + Apache rolled into an installer, so its "trustworthiness" will be the same as Apache's and subversion's.
Ben Collins
2009-05-11 14:30:37
oh how long have your company been using it? is it many people using it and it is still reliable?
動靜能量
2009-05-11 15:30:58
we've been using it a few months. Shortly after I started, I made a stink about VSS (because it's really terrible). We have about 8-10 people using it and it's been just fine. Really.....I don't know what you're worried about. Underneath the hood, it's just the stock svnserve, like I said in my answer.
Ben Collins
2009-05-11 16:15:11
I'm using it, I imported our old VSS DB into it 18+ months ago. Its been flawless since on a 12Gb repo with 310,000 revisions.
gbjbaanb
2010-05-14 12:18:24
Been using it since August 2008 with no major problems.
Eddie
2010-05-14 12:48:32
+1
A:
Can you define Trustworthy? Do you mean not likely to crash or corrupt data, or do you mean able to handle a lot of traffic, or do you mean not exploited or exploitable easily?
SVN + Apache fare well in each of those categories, but I don't know what the custom portion of the installer has in it.
John Weldon
2009-05-11 14:33:42
i mean in terms of... is it as good as installing apache and subversion server myself from scratch?i suppose corrupting data and data security also count towards this too... whether it is related to the Apache + SVN server combination or the packaging of them by Visual SVN.
動靜能量
2009-05-11 14:37:57
It's all taken care of for you. That's the whole point of VisualSVN. There's very little to configure, and what little there is can be done by the admin tools included with VisualSVN.
Ben Collins
2009-05-11 18:35:14
+1
A:
We've been using it for a while without any issues; apart from the GUIs it's the same Apache/SVN base as every other server. It's nice being able to upgrade it with an MSI, and it has a nice Windows GUI for handling AD integration, certificate management etc. They also seem to be pretty quick at getting updates out. The only two negatives (certainly when I last checked) are:
- You are restricted to http/https access unless you want to manually set things up.
- When you decide you want https you are stick with JUST https, you don't seem to be able to run both http and https together.
Steven Robbins
2009-05-11 14:38:04
+4
A:
I've been using VisualSVN Server for a few weeks along with the VisualSVN client for Visual Studio. It has been trouble free and setting it up was easier than falling off a log. The management console lets you create repositories and folders, perform simple operations on them (delete, import, etc) and set user permissions (Active Directory Integrated or SVN authentication). It just works and does just enough and no more. I think they got it exactly right.
I'm a Windows Server guy so I was a bit dubious about using Apache, but it is completely transparent and integrated into VisualSVN, if they hadn't mentioned it on the web site, I'd never have known I was running Apache. If you wanted to host other things in Apache too, then I guess you'd want to do things differently, but I wanted a turnkey solution and VisualSVN provided it.
Tim Long
2009-05-11 15:30:44
+3
A:
I've had one big issue with it.
The issue I have is that the repositories are saved with Windows line endings (Carriage Return + Line Feed) instead of the Linux line endings (Line Feed) when the repositories are in the file system format.
This has prevented me from porting the repository (with all revisions in tact) from a local network Windows server VisualSVN hosting to a public Linux SVN hosting. Since all my code is in Windows code if I change the Windows line endings to the Linux ones I mess up all my code. SVN admin tools in Linux won't recognize the repository if I don't convert them though.
So I can move an export of the code into a public repository, but I lose all the previous revision history which is a huge inconvenience but not a show-stopper.
Jesse Dearing
2009-05-11 15:43:24
As far as I know the fsfs files always use '\n' line endings to make them platform independenti, but even if this is not the case you can *ALWAYS* dump the repository and load that on the other operating system. Are you sure you use the native windows tools (and not the cygwin versions)? Cygwin sometimes breaks the explicit line ending support in Subversion when enabling their own conversion support.
Bert Huijben
2009-05-12 07:27:51
Using the native tools (Collabnet release) to dump a repository that was created by VisualSVN I get:'vnadmin: Unknown FS type 'fsfs I didn't add those single quotes in the output from svnadmin. Using a hex editor on the db/fs-type file of the repository it has the 0D 0A (\r\n) at the end of fsfs. When I look at a repository made by TortoiseSVN, the same file has just the 0A (\n) after fsfs.I suspect it is on the VisualSVN implementation since I have successfully migraged a TortoiseSVN repository to a Linux environment.I was using VisualSVN Server 1.5.3.
Jesse Dearing
2009-05-12 17:29:37