对 CollabNet Subversion Edge 进行投票后，通过 Web 前端进行设置和管理非常简单。 如果必须的话，我很乐意编辑配置文件，尤其是来自 Linux 环境，但最好不要被要求这样做 - CollabNet 让这变得简单。
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.
但是，我使用 Apache httpd 来访问我的 Windows Active Directory。 我设置了我的用户，因此他们的 Windows 帐户和密码就是他们的 Subversion 帐户和密码。 我设置了 Active Directory 安全组或 Active Directory Exchange 组作为我的授权数据库。 如果用户是该组的成员，他们可以通过 Windows 登录访问存储库。 如果没有，他们就无权访问。 干净简单。 我不再从事用户授权业务，这让我有更多时间玩Candy Crush..我的意思是..其他CM工作。
否则，我还不如使用 svnserve：它比 Apache httpd 更快，更容易设置，也更稳定。
如果您不打算使用 Active Directory 作为授权后端，并且您是技术人员，并且不介意弄脏双手，我会使用 play svnserve （并将其设置为 不需要任何这些包。
Windows 服务如果您 如果您打算使用 Active Directory 作为您的授权后端（为什么不呢？），我会使用 CollabNet Subversion Edge 来帮助设置 Apache httpd 和 Subversion，并通过 Apache httpd 通过 LDAP 设置 Active Directory。真的那么困难，一旦完成，您可能永远不必再接触有关集成 Apache httpd/Subversion/LDAP/ActiveDirectory 的文档可以轻松地实现。 。
All of these solutions setup the standard Apache HTTPD server with Subversion integration. They do no real magic.
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.
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.
Otherwise, I might as well just use svnserve: It's faster than Apache httpd, much easier to setup, and more stable too.
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.
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.
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.
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.
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.
发布评论
评论（7）
我们选择 VisualSVN 因为它可以轻松使用 Windows 身份验证，而不需要单独的 SVN 用户。
其他好处是易于使用的 GUI，用于权限管理和管理 SVN 挂钩。
我不太喜欢的一件事是 Web GUI。 据我所知，您无法查看基于网络的差异，所以如果这有影响的话......
We chose VisualSVN bec it makes it easy to use windows authentication instead of having a separate SVN user.
Other benefits is an easy to use GUI for permission management and for managing SVN hooks.
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....
我经营 Windows 商店的朋友对 VisualSVN 评价很高
My friends who run a Windows shop speak highly of VisualSVN
我刚刚根据 win32svn 服务器/04/setting-up-subversion-on-windows.html">这篇文章，作者：Jeff Atwood。
与 VisualSVN 相比，win32svn 与 Windows 的集成并不那么紧密，它面向终端使用，并且在 Apache 许可证下开源。
I've just configured win32svn server according to this article by Jeff Atwood.
In contrast to VisualSVN win32svn is not so tightly integrated to Windows, orientated on terminal usage and open sourced under Apache License.
对 CollabNet Subversion Edge 进行投票后，通过 Web 前端进行设置和管理非常简单。 如果必须的话，我很乐意编辑配置文件，尤其是来自 Linux 环境，但最好不要被要求这样做 - CollabNet 让这变得简单。
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.
所有这些解决方案都设置了带有 Subversion 集成的标准 Apache HTTPD 服务器。 他们没有施展真正的魔法。
UberSVN 和 VisualSVN 提供了一个漂亮的前端界面，但在幕后，它只是标准的 Apache 设置。 如果您不是 CM，并且不希望这成为您的工作，那么这也是一个不错的选择。 但是，永远不要试图在他们背后调整配置。 他们要么恢复更改，要么把事情搞砸。
但是，我使用 Apache httpd 来访问我的 Windows Active Directory。 我设置了我的用户，因此他们的 Windows 帐户和密码就是他们的 Subversion 帐户和密码。 我设置了 Active Directory 安全组或 Active Directory Exchange 组作为我的授权数据库。 如果用户是该组的成员，他们可以通过 Windows 登录访问存储库。 如果没有，他们就无权访问。 干净简单。 我不再从事用户授权业务，这让我有更多时间
玩Candy Crush..我的意思是..其他CM工作。否则，我还不如使用 svnserve：它比 Apache httpd 更快，更容易设置，也更稳定。
如果您不打算使用 Active Directory 作为授权后端，并且您是技术人员，并且不介意弄脏双手，我会使用 play
svnserve（并将其设置为 不需要任何这些包。Windows 服务如果您 如果您打算使用 Active Directory 作为您的授权后端（为什么不呢？），我会使用 CollabNet Subversion Edge 来帮助设置 Apache httpd 和 Subversion，并通过 Apache httpd 通过 LDAP 设置 Active Directory。真的那么困难，一旦完成，您可能永远不必再接触有关集成 Apache httpd/Subversion/LDAP/ActiveDirectory 的文档可以轻松地实现。 。
我建议您查看在线 Subversion 文档 并仔细阅读 如果考虑使用 svn 命令行客户端让您感到头晕，那么使用 VisualSVN 或 UberSVN，让他们为您处理一切。 如果您不介意使用计算机度过 1990 年，那么请忘记漂亮的前端，而使用 CollabNet Edge。
还有一件事，我不喜欢 CollabNet Edge 附带的 ViewVC。 它必须使用
file://协议，并且必须与 Subversion 服务器软件在同一服务器上运行。 相反，我更喜欢Sventon。 它可以在单独的服务器上运行，并且您可以使用与标准 Subversion 凭据相同的凭据。 另外，我更喜欢这个界面。All of these solutions setup the standard Apache HTTPD server with Subversion integration. They do no real magic.
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.
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.Otherwise, I might as well just use
svnserve: It's faster than Apache httpd, much easier to setup, and more stable too.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.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.
I suggest you look at the on line Subversion Documentation and go through it. If thinking about using the
svncommand 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.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.我们将 Apache SSPI 模块与 Collab.Net subversion 服务器结合使用。
对我们来说效果很好。
We use an Apache SSPI module with the Collab.Net subversion server.
Has worked perfectly for us.
尝试 UberSVN http://www.wandisco.com/ubersvn/download#windows
唯一的缺点是需要大量服务器内存。 我尝试过的最好的免费 SVN 服务器。 VisualSVN 免费版也可以。
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.