On the SVN Windows binaries download page, there are a few to choose from:
在SVN Windows二进制文件下载页面上,有几个可供选择:
http://subversion.tigris.org/getting.html#windows
Are there pros and cons to the different versions provided by the different organizations? Is there anything I should look out for?
不同组织提供的不同版本是否有利有弊?有什么我应该注意的吗?
Mainly, I just want something free that I will be running off my Vista laptop. Then I will probably do backups of the SVN files from time to time to an external hard drive.
主要是,我只是想要一些免费的东西,我将从我的Vista笔记本电脑上运行。然后我可能会不时地将SVN文件备份到外部硬盘。
7 个解决方案
#1
We chose VisualSVN bec it makes it easy to use windows authentication instead of having a separate SVN user.
我们之所以选择VisualSVN,是因为它可以轻松使用Windows身份验证,而不是拥有单独的SVN用户。
Other benefits is an easy to use GUI for permission management and for managing SVN hooks.
其他好处是易于使用的GUI用于权限管理和管理SVN挂钩。
The one thing I'm not a real fan of is the web GUI. As far as I know you cannot view web based diffs, so if that makes a difference....
我不是真正的粉丝的一件事是Web GUI。据我所知,你不能查看基于网络的差异,所以如果这有所作为....
#3
I've just configured win32svn server according to this article by Jeff Atwood.
我刚刚根据Jeff Atwood的这篇文章配置了win32svn服务器。
In contrast to VisualSVN win32svn is not so tightly integrated to Windows, orientated on terminal usage and open sourced under Apache License.
与VisualSVN相比,win32svn没有与Windows紧密集成,以终端使用为导向,在Apache License下开源。
#4
All of these solutions setup the standard Apache HTTPD server with Subversion integration. They do no real magic.
所有这些解决方案都使用Subversion集成设置标准的Apache HTTPD服务器。他们没有真正的魔力。
UberSVN and VisualSVN provide a pretty front end interface, but behind the scenes, it's just standard Apache setup. If you are not a CM, and don't want that to be your job, that's not a bad alternative. However, do not ever try to tweak the configuration behind their backs. They will either revert the changes, or really mess things up.
UberSVN和VisualSVN提供了一个漂亮的前端界面,但在幕后,它只是标准的Apache设置。如果你不是CM,并且不希望那是你的工作,那不是一个糟糕的选择。但是,不要试图调整背后的配置。他们要么会恢复变化,要么真的搞砸了。
However, I use Apache httpd in order to access my Windows Active Directory. I setup my users, so their Windows account and password are their Subversion account and password. I setup a Active Directory Security Group or a Active Directory Exchange Group as my authorization database. If a user is a member of this group, they have access to the repository via their Windows login. If not, they don't have access. Clean and simple. I am no longer in the user authorization business which gives me more time to
play Candy Crush
..I mean.. other CM work.
但是,我使用Apache httpd来访问我的Windows Active Directory。我设置了我的用户,因此他们的Windows帐户和密码是他们的Subversion帐户和密码。我将Active Directory安全组或Active Directory Exchange组设置为我的授权数据库。如果用户是该组的成员,则他们可以通过Windows登录访问存储库。如果没有,他们就无法访问。干净简单。我不再在用户授权业务,这让我有更多时间玩Candy Crush ..我的意思是..其他CM工作。
Otherwise, I might as well just use svnserve: It's faster than Apache httpd, much easier to setup, and more stable too.
否则,我不妨使用svnserve:它比Apache httpd更快,更容易设置,也更稳定。
If you're not going to use Active Directory as your authorization backend, you are technical, and don't mind getting your hands a bit dirty, I would use either play svnserve (and set it up as a Windows Service. No need for any of these packages.
如果你不打算使用Active Directory作为你的授权后端,你是技术人员,不介意让你的手有点脏,我会使用播放svnserve(并将其设置为Windows服务。不需要任何这些包。
If you are going to use Active Directory as your authorization backend (and why not?), I would use CollabNet Subversion Edge to help setup Apache httpd and Subversion and do all of my configuration manually. Setting up Active Directory via LDAP via Apache httpd isn't really that difficult, and once done, you probably never have to touch again. The documentation on integrating Apache httpd/Subversion/LDAP/ActiveDirectory can easily be found.
如果您打算使用Active Directory作为授权后端(为什么不使用?),我会使用CollabNet Subversion Edge帮助设置Apache httpd和Subversion并手动完成所有配置。通过Apache httpd通过LDAP设置Active Directory并不是那么困难,一旦完成,您可能永远不必再次触摸。可以轻松找到有关集成Apache httpd / Subversion / LDAP / ActiveDirectory的文档。
I suggest you look at the on line Subversion Documentation and go through it. If thinking about using the svn command line client makes you woozy, then get VisualSVN or UberSVN and let them take care of things for you. If you don't mind going all 1990 with your computer, then forget about the pretty front ends, and use CollabNet Edge.
我建议你看看在线Subversion文档并仔细阅读。如果考虑使用svn命令行客户端让你恍惚,那么获取VisualSVN或UberSVN并让他们为你处理事情。如果您不介意使用计算机全部使用1990年,那么请忘记漂亮的前端,并使用CollabNet Edge。
One more thing, I am not a fan of ViewVC that comes with CollabNet Edge. It has to use file:// protocol and must run on the same server as your Subversion server software. Instead, I prefer Sventon. It can run on a separate server, and you can use the same credentials as your standard Subversion credentials. Plus, I like the interface a bit better.
还有一件事,我不是CollabNet Edge附带的ViewVC的粉丝。它必须使用file://协议,并且必须在与Subversion服务器软件相同的服务器上运行。相反,我更喜欢Sventon。它可以在单独的服务器上运行,您可以使用与标准Subversion凭据相同的凭据。另外,我更喜欢界面。
#5
Putting in a vote for CollabNet Subversion Edge, it's dead simple to set up and administer via a web frontend. I'm comfortable editing config files if I must, especially coming from a Linux environment, but it's nice not to be required to do so - CollabNet makes that easy.
对CollabNet Subversion Edge进行投票,通过Web前端进行设置和管理非常简单。如果必须的话,我很乐意编辑配置文件,特别是来自Linux环境,但不要求这样做很好--CollabNet让这很容易。
#6
We use an Apache SSPI module with the Collab.Net subversion server.
我们将Apache SSPI模块与Collab.Net subversion服务器一起使用。
Has worked perfectly for us.
对我们来说工作得很好。
#7
Try UberSVN http://www.wandisco.com/ubersvn/download#windows The only downside is that is requires lot of server memory. Best free SVN server I ever tried. VisualSVN free version is OK as well.
试试UberSVN http://www.wandisco.com/ubersvn/download#windows唯一的缺点是需要大量的服务器内存。我曾尝试过的最好的免费SVN服务器。 VisualSVN免费版也可以。
#1
We chose VisualSVN bec it makes it easy to use windows authentication instead of having a separate SVN user.
我们之所以选择VisualSVN,是因为它可以轻松使用Windows身份验证,而不是拥有单独的SVN用户。
Other benefits is an easy to use GUI for permission management and for managing SVN hooks.
其他好处是易于使用的GUI用于权限管理和管理SVN挂钩。
The one thing I'm not a real fan of is the web GUI. As far as I know you cannot view web based diffs, so if that makes a difference....
我不是真正的粉丝的一件事是Web GUI。据我所知,你不能查看基于网络的差异,所以如果这有所作为....
#2
My friends who run a Windows shop speak highly of VisualSVN
我经营Windows商店的朋友高度评价VisualSVN
#3
I've just configured win32svn server according to this article by Jeff Atwood.
我刚刚根据Jeff Atwood的这篇文章配置了win32svn服务器。
In contrast to VisualSVN win32svn is not so tightly integrated to Windows, orientated on terminal usage and open sourced under Apache License.
与VisualSVN相比,win32svn没有与Windows紧密集成,以终端使用为导向,在Apache License下开源。
#4
All of these solutions setup the standard Apache HTTPD server with Subversion integration. They do no real magic.
所有这些解决方案都使用Subversion集成设置标准的Apache HTTPD服务器。他们没有真正的魔力。
UberSVN and VisualSVN provide a pretty front end interface, but behind the scenes, it's just standard Apache setup. If you are not a CM, and don't want that to be your job, that's not a bad alternative. However, do not ever try to tweak the configuration behind their backs. They will either revert the changes, or really mess things up.
UberSVN和VisualSVN提供了一个漂亮的前端界面,但在幕后,它只是标准的Apache设置。如果你不是CM,并且不希望那是你的工作,那不是一个糟糕的选择。但是,不要试图调整背后的配置。他们要么会恢复变化,要么真的搞砸了。
However, I use Apache httpd in order to access my Windows Active Directory. I setup my users, so their Windows account and password are their Subversion account and password. I setup a Active Directory Security Group or a Active Directory Exchange Group as my authorization database. If a user is a member of this group, they have access to the repository via their Windows login. If not, they don't have access. Clean and simple. I am no longer in the user authorization business which gives me more time to
play Candy Crush
..I mean.. other CM work.
但是,我使用Apache httpd来访问我的Windows Active Directory。我设置了我的用户,因此他们的Windows帐户和密码是他们的Subversion帐户和密码。我将Active Directory安全组或Active Directory Exchange组设置为我的授权数据库。如果用户是该组的成员,则他们可以通过Windows登录访问存储库。如果没有,他们就无法访问。干净简单。我不再在用户授权业务,这让我有更多时间玩Candy Crush ..我的意思是..其他CM工作。
Otherwise, I might as well just use svnserve: It's faster than Apache httpd, much easier to setup, and more stable too.
否则,我不妨使用svnserve:它比Apache httpd更快,更容易设置,也更稳定。
If you're not going to use Active Directory as your authorization backend, you are technical, and don't mind getting your hands a bit dirty, I would use either play svnserve (and set it up as a Windows Service. No need for any of these packages.
如果你不打算使用Active Directory作为你的授权后端,你是技术人员,不介意让你的手有点脏,我会使用播放svnserve(并将其设置为Windows服务。不需要任何这些包。
If you are going to use Active Directory as your authorization backend (and why not?), I would use CollabNet Subversion Edge to help setup Apache httpd and Subversion and do all of my configuration manually. Setting up Active Directory via LDAP via Apache httpd isn't really that difficult, and once done, you probably never have to touch again. The documentation on integrating Apache httpd/Subversion/LDAP/ActiveDirectory can easily be found.
如果您打算使用Active Directory作为授权后端(为什么不使用?),我会使用CollabNet Subversion Edge帮助设置Apache httpd和Subversion并手动完成所有配置。通过Apache httpd通过LDAP设置Active Directory并不是那么困难,一旦完成,您可能永远不必再次触摸。可以轻松找到有关集成Apache httpd / Subversion / LDAP / ActiveDirectory的文档。
I suggest you look at the on line Subversion Documentation and go through it. If thinking about using the svn command line client makes you woozy, then get VisualSVN or UberSVN and let them take care of things for you. If you don't mind going all 1990 with your computer, then forget about the pretty front ends, and use CollabNet Edge.
我建议你看看在线Subversion文档并仔细阅读。如果考虑使用svn命令行客户端让你恍惚,那么获取VisualSVN或UberSVN并让他们为你处理事情。如果您不介意使用计算机全部使用1990年,那么请忘记漂亮的前端,并使用CollabNet Edge。
One more thing, I am not a fan of ViewVC that comes with CollabNet Edge. It has to use file:// protocol and must run on the same server as your Subversion server software. Instead, I prefer Sventon. It can run on a separate server, and you can use the same credentials as your standard Subversion credentials. Plus, I like the interface a bit better.
还有一件事,我不是CollabNet Edge附带的ViewVC的粉丝。它必须使用file://协议,并且必须在与Subversion服务器软件相同的服务器上运行。相反,我更喜欢Sventon。它可以在单独的服务器上运行,您可以使用与标准Subversion凭据相同的凭据。另外,我更喜欢界面。
#5
Putting in a vote for CollabNet Subversion Edge, it's dead simple to set up and administer via a web frontend. I'm comfortable editing config files if I must, especially coming from a Linux environment, but it's nice not to be required to do so - CollabNet makes that easy.
对CollabNet Subversion Edge进行投票,通过Web前端进行设置和管理非常简单。如果必须的话,我很乐意编辑配置文件,特别是来自Linux环境,但不要求这样做很好--CollabNet让这很容易。
#6
We use an Apache SSPI module with the Collab.Net subversion server.
我们将Apache SSPI模块与Collab.Net subversion服务器一起使用。
Has worked perfectly for us.
对我们来说工作得很好。
#7
Try UberSVN http://www.wandisco.com/ubersvn/download#windows The only downside is that is requires lot of server memory. Best free SVN server I ever tried. VisualSVN free version is OK as well.
试试UberSVN http://www.wandisco.com/ubersvn/download#windows唯一的缺点是需要大量的服务器内存。我曾尝试过的最好的免费SVN服务器。 VisualSVN免费版也可以。