颠覆服务器与通过乌龟访问网络存储库
目前我的团队中有 5 名开发人员，我们都通过网络上计算机 X 上的共享驱动器访问存储库。 由于我们都可以访问计算机 X，并且我们可以管理谁可以访问计算机 X，谁不能访问计算机 X，所以我们可以管理谁可以访问我们的存储库。
我的问题是：如果我设置了 subversion 服务器，我是否可以获得任何我还没有的功能？ 存储库已经内置了用户/密码控制。
- 我是否能够跟踪谁当前已签出文件？
- 我是否可以获得向多个人授予锁的能力（仅
用户 a 和 b 锁定了一个文件，其他用户无法查看该文件 文件）？ - 我能获得安全感吗？
看来我没有，因为，再一次，我已经拥有用户/组/密码控制而无需服务器。
请告诉我。 我正在决定创建服务器是否有任何优势。
谢谢， 吉布
There are currently 5 developers on my team and we all access a repository through a shared drive on computer X which is on our network. Since we all have access to computer X, and we can manage who has and who doesn't have access to computer X, we can manage who can access our repository.
My question is this: If I set up a subversion server, do I gain any functionality that I don't already have? The repositories already have user/passwd control built right in.
- Do I gain the ability to track who currently has a file checked out?
- Do I gain the ability to give a lock to more than one person (Only
users a and b have a file locked, no other users can check out that
file)? - Do I gain any security?
It seems like I don't, because, again, I already have user/group/passwd control without a server.
Please let me know. I'm deciding whether or not there's any advantage creating a server.
Thanks,
jbu
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
是的，您会收获很多：您降低了丢失所有数据的风险！
请参阅有关访问网络共享上的存储库。
Yes, you would gain a lot: you reduce the risk of losing all your data!
See the docs (and warnings) about accessing a repository on a network share.
当您通过 file:/// URL 访问存储库时，subversion 库将假定存储库在本地磁盘上可用，并且不会尝试（甚至无法）最小化网络 I/O。 因此，对于某些需要读取大量数据以确定需要发送到客户端的部分的操作，通过 svn:/// URL 访问存储库快得多
svn switch< 的情况/a> 命令。我不敢对 http:// 访问说同样的话。 在 svn 1.5 中，http 协议相对繁琐且效率低下。 有计划来改进 svn 1.7
When you access the repository through a file:/// URL, the subversion libraries will assume the repository is available on a local disk and will not attempt (or even be able) to minimize network I/O. Accessing the repository through a svn:/// URL is therefore much faster for certain operations where a lot of data needs to be read just to determine the fraction that needs to be send to the client, as is the case for the
svn switchcommand.I don't dare say the same about http:// access. The http protocol is relatively chatty and inefficient in svn 1.5. There are plans to improve this for svn 1.7
通常，您不会在 SVN 中“签出”文件。 也就是说，您在处理它们时不会锁定它们。
然而，您可以获得一些东西（这些只是我的想法）：
注意，但是，大多数或所有这些好处并不是 subversion 所独有的，而是可以从大多数现代版本控制系统中获得。
Generally, you don't "check out" files in SVN. That is, you don't lock them while working on them.
You gain several things however, (these are just from the top of my head):
Note however, that most or all of these benefits are not unique to subversion, but can be gained from most of the modern version control systems.
是的，您可以做一些额外的事情：
编辑：不确定您是否'当前正在通过文件共享使用 Subversion，或者仅使用普通文件共享。 （SVN 也可以使用 file:/// URI）。
Yes, you could do several additional things:
edit: Unsure if you're using subversion currently over a file-share, or only using a plain file share. (SVN can use file:/// URIs as well).