SVN subversion 设置和身份验证问题
我对版本控制比较陌生，我需要一些帮助来确定这是否是正确的设置。
我正在使用 Sourceforge、TortoiseSVN 和 DynDNS 中的“Subversion for Windows”。我们有一台“服务器机器”，用来安装所有这些。我们希望能够通过网络共享存储库并从家里访问它。我们没有可供使用的网络服务器。
文件夹结构如下：
C:\SVN\project-name\trunk
C:\SVN\project-name\branches and so on...
在本地计算机上测试运行时，我能够安装所有内容并使用如下地址成功导入和下载存储库的副本：
svn://my-dyndns-addr/SVN-folder/project-name/trunk
为了加快进程，我没有运行 svnserve .exe 文件作为服务并简单地使用此命令：
svnserve.exe --daemon
这工作得很好。 DynDNS 连接似乎也能正常工作，我可以从我们的任何工作计算机上 ping 它。 “conf”目录中的配置文件均已使用新的用户名和密码进行了适当修改。
然后是时候在服务器上重复这个过程了，我以类似的方式安装和配置了所有内容。我所做的唯一更改是按照本指南。服务安装正常，我可以连接到存储库，但身份验证失败。我仍然能够 ping 通 DynDNS 地址和 SVN 地址。
所以我的问题是：我是否遗漏了身份验证过程的某些部分？为什么在如此相似的设置下我可以连接到我的机器上的 SVN 服务器，但不能连接到服务器上？这是一个好的设置吗？除了拥有良好的用户名和密码之外，我还应该担心安全性吗？有什么我可能会忽略的小事情吗？这对我来说是全新的，所以我大部分时间都在“修补”。
谢谢。
最后几点说明：我正在远程连接到服务器，并且我已经重新启动了服务和计算机几次。
I am relatively new to revision control and I need some help deciding if this is the proper set up.
I am using "Subversion for Windows" from Sourceforge, TortoiseSVN and DynDNS. We have a "server machine" we're using to install all of this on. We want to be able to share the repository over the network and access it from home. We do not have a web server available to use.
The folder structure is like this:
C:\SVN\project-name\trunk
C:\SVN\project-name\branches and so on...
On the test run on my local machine I was able to install everything and successfully import and download copies of our repository using an address like such:
svn://my-dyndns-addr/SVN-folder/project-name/trunk
For the sake of expediting the process I didn't run the svnserve.exe file as a service and simply used this command:
svnserve.exe --daemon
This worked fine. The DynDNS connection seems to work as well and I can ping it from any of our work machines. The configuration files in the "conf" directory have all been modified appropriately with a new username and password.
Then it was time to repeat this process on the server and I installed and configured everything similarly. The only change I made was installing svnserve.exe as a service following this guide. The service installed fine and I can connect to the repository, but the authentication is failing. Again I am still able to ping the DynDNS address and the SVN address.
So my questions are: is there some part of the authentication process I'm missing? How come with such similar setups I can connect to the SVN server on my machine but not on the server? And is this a good setup? Should I be concerned about security beyond having good usernames and passwords? Are there any little things I might be overlooking? This is all new to me so I've mostly been "tinkering" around.
Thanks.
A couple last notes: I am remoting into the server and I've restarted the service and computer a couple times now.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
听起来该服务无权访问密码文件。
服务通常作为特殊用户运行，例如网络服务。因此，它可能无法访问您的 subversion 根目录。
您可以通过使服务以普通用户身份运行或授予网络服务对根目录的访问权限来解决此问题。
It sounds like the service doesn't have access to the password file.
Services usually run as a special user, such as Network Service. As such, it may not have access to your subversion root directory.
You can fix that by making your service run as a regular user, or by granting Network Service access to your root directory.
不要在 SVN 服务器设置上浪费时间。
Visual SVN
Collabonet Subversion Edge
这些都是免费的！提供 Web 服务器和 https 安全性。
Don't waste your time with SVN server setup.
Visual SVN
Collabonet Subversion Edge
These are free! Provided with the web server and https security.
我不想回答我自己的问题，但对于那些可能遇到类似问题的人来说，发生的事情是这样的：
首先，按照 9dan 的建议，我将我的 subversion 包切换到了 Collab 的。安装更容易，服务会自动安装。谢谢。
接下来，我不认为访问文件夹的服务存在问题。事实上，在我做了一些不同的测试之后，我几乎可以肯定没有。最终的问题是我在conf/passwd 文件中选择的用户名。为了简单起见，我使用了我的学生网络帐户名。在最后的努力中，我改变了它，重新启动服务器，它工作了！它看起来仍然有点做作，在我放心离开它之前需要更多的照顾，但至少它正在工作！
最后一点，这可能只会影响少数人，但 Collab 安装的服务之一是 Apache。我运行了 XAMPP 服务，但它们存在冲突。请务必检查您的服务以了解哪些服务正在运行。就我而言，我不需要 Apache 来进行颠覆，所以我禁用了它。
感谢您的回复！希望这对一些人有帮助。
I hate to answer my own question, but for those that might experience similar problems, here is what happened:
First off, taking 9dan's advice I switched my subversion package to Collab's. Easier install and the services installed automatically. Thanks.
Next I don't believe there was an issue with the service accessing the folders. In fact I'm almost positive there wasn't after some various testing I did. What the problem ended up being was my choice of username in the conf/passwd file. I had for the sake of simplicity, used my student network account name. In a last ditch effort I changed it, restarted the server and it worked! It still seems a little hokey and will require some more care before I feel comfortable leaving it, but at least it's working!
On a final note, and this may only affect a few people, but one of the services installed by Collab is Apache. I had XAMPP services running and they conflicted. Be sure to check your services to see which is running. In my case, I don't need Apache for subversion so I disabled it.
Thanks for the replies! Hope this helps some people.