替代 Hamachi 以进行 SVN 访问
我的公司多年来一直使用 Hamachi 访问我们的 SVN 存储库。我们是一个规模虽小但分布广泛的开发团队，每个程序员都在不同的国家/地区在家工作。服务器由我们中央办公室的非技术人员托管。 Hamachi 在这里很有用，因为它有 GUI 并支持远程管理。
这个系统在一段时间内运行良好，但最近我搬到了一个网速很差的国家。 Hamachi 在 99% 的情况下将不再连接 - 相反，我收到一条无法解决的“正在探测...”消息。这肯定是一个延迟问题，因为当我跨越边界并使用速度更快的不同 ISP 进行连接时，同一台笔记本电脑将毫无问题地连接。
所以我真的需要用其他一些可以更好地处理延迟的 VPN/协议来替换 Hamachi。管理存储库的技术人员不太习惯安装和配置 Apache 或 IIS，因此看起来 HTTP 已经过时了。我试图说服我的老板选择一家网络托管公司，但他不信任拥有我们来源的第三方。
任何其他推荐的访问我们的 SVN 存储库的选项/体验都像 Hamachi 一样简单设置；但更能容忍网络延迟问题？
My company has been using Hamachi to access our SVN repository for a number of years. We are a small yet widely distributed development team with each programmer in a different country working from home. The server is hosted by a non-techie in our central office. Hamachi is useful here since it has a GUI and supports remote management.
This system worked well for a while, but recently I have moved to a country with poor internet speeds. Hamachi will no longer connect 99% of the time - instead I get a "Probing..." message that doesn't resolve. It's certain to be a latency issue, as the same laptop will connect without problems when I cross the border and connect using a different ISP with better speeds.
So I really need to replace Hamachi with some other VPN/protocol that handles latency better. The techie managing the repository is not comfortable installing and configuring Apache or IIS, so it looks like HTTP is out. I tried to convince my boss to go for a web hosting company, but he doesn't trust a 3rd party with our source.
Any other recommended options / experiences out there for accessing our SVN repos that would be as simple as Hamachi for setup; but be more tolerant of network latency issues?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
也许对你的团队要求有点高，但如果你有一个分布式团队，那么你可以切换到分布式版本控制系统（例如 Mercurial 或 Git）。这些不需要太多使用网络，并且您不会遇到延迟问题。不过，这是一个全新的范例，您团队的开发流程必须改变，因此您可能认为它不适合您的情况。
Perhaps it's a bit much to ask of your team, but if you have a distributed team then you could switch to a distributed version control system (eg. Mercurial or Git). These don't need to use the network so much and you won't suffer from latency problems. It is an entirely new paradigm though and your team's development processes will have to change, so you might not consider it appropriate in your case.
首先我应该问为什么你需要 VPN。 Subversion 可以通过 HTTPS 运行，因此只要您在服务器上打开正确的端口，就不应该出现任何安全或连接问题。
假设您确实需要 VPN，我发现很难相信对 Apache 感到不舒服的管理员会更轻松地安装全新的 VPN 系统（在我看来，更加复杂和棘手）。
First I should ask why you need a VPN in the first place. Subversion can operate over HTTPS, so as long as you open the proper port on the server there shouldn't be any security or connectivity issues.
Assuming that you do need a VPN, I find it difficult to believe that an administrator uncomfortable with Apache would be more comfortable installing a whole new VPN system (much more complicated and tricky, in my estimation).