源代码控制管理器后端
您认为源代码控制管理器后端更好的方法是什么？我正在权衡文件系统与托管 Subversion 服务。 托管颠覆--> （我公司已经有另一个小组负责此事） 优点： * 我们这边零维护 * 自动备份和恢复 * 自动备份和文件冗余的可靠性。 * 内置文件历史查看、文件合并、文件比较
另一方面，文件系统虽然没有上述功能，但要简单得多。此外，如果文件托管在已备份的 Linux 计算机上，则可以解决文件系统崩溃问题。 Subversion 将需要工作副本，这些副本将位于同一台 Linux 计算机上，因此不需要额外的层。
各位，我正在寻找更强有力的理由来解释为什么我应该采用 Subversion，而不是让事情变得简单并使用文件系统。
让我知道你的意见。非常感谢，加布里埃尔。
PS：我探索了一些商业源管理器，并决定走这条路，因为它更适合我们的需求。
What do you think is a better approach for Source Control Manager Backend. I am weighing File system vs Hosted Subversion service.
Hosted Subversion--> (My company already has another group taking care of this)
Advantages:
* Zero maintenance on our end
* Auto-backup and recovery
* Reliability by auto-backup and file redundancy.
* File history view in built, file merge, file diff
On the other hand, while File system does not have the featured mentioned above but is much more simpler. Moreover, if files are hosted on Linux machine, which is backed up, it takes care of file system crash issues. Subversion will need working copies, which are going to be on this same Linux machine, and hence the need to not have an extra layer.
Folks, I am looking for stronger reasons why I should take Subversion instead of keeping thing simple and going with File System.
Let me know your opinions. Very thanks in advance, Gabriel.
PS: I have explored few Commercial Source Manager, and have decide to go this route as it better suits our need.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我不同意您的说法，即使用文件系统来存储源代码更简单。当多个开发人员需要同时处理同一个文件时，您会怎么做？当您需要撤销更改时，您会怎么做？真正的源代码控制系统（Subversion 或其他）的好处有很多。
I would disagree with your statement that using a file system to store your sources is simpler. What will you do when more than one developer needs to work on the same file at the same time? What will you do when you need to back out a change? The benefits of a real source control system (Subversion or other) are many.
使用源代码控制。句号。
出于一系列原因，有大量文章，但从 http://www.codinghorror.com/blog/2006/08/source-control-anything-but-sourcesafe.html 并用于 ie http://www.mactech.com/articles/mactech/Vol.14/14.06/VersionControlAndTheDeveloper/
Use source control. Full stop.
For a list of reasons, there are ton of articles out there, but start with http://www.codinghorror.com/blog/2006/08/source-control-anything-but-sourcesafe.html and for i.e. http://www.mactech.com/articles/mactech/Vol.14/14.06/VersionControlAndTheDeveloper/
我什至懒得列出原因。这一切都归结为这一点：
您是一名程序员
，您每天处理的复杂性甚至使最复杂的 SCM（caugh git caugh）的复杂性相形见绌。
使用文件系统进行机会控制类似于使用记事本进行编程：它适用于小型项目，但缺乏功能（和安全性等）很快就会开始花费您大量时间。
也就是说，我确实为推荐一些没有科学支持的东西感到难过。对不起 ：（
I won't even bother to list the reasons. It all comes down to this:
you're a programmer
The complexity you deal with every day dwarfs the the complexity of even the most (caugh git caugh) complex SCM.
Using the filesystem for chance control is similar to programming with notepad: it'll work for small projects, but the lack of features (and safety, etc) will very quickly start to cost you big time.
That said, I do feel bad for recommending something without science to back it up. Sorry :(