我想从镜像中签出，但在没有 svn sw --relocate 命令的情况下提交给主服务器
我想从镜像中签出，但在没有 svn sw 的情况下提交给主控，这可能吗？
使用 svn sw --relocate 我可以做到这一点，但我想在提交期间自动从从服务器更改为主服务器。 svn checkout 将如何工作（过程） 任何人都可以解释一下这一点。
退房时不能设置从服务器的目标IP或主IP吗？有脚本吗？
我正在尝试从主服务器本身同步数据，但出现以下错误：
Warning: post-commit hook failed (exit code 255) with output: Host key verification failed.
我将从服务器的 svnsync同步文件:///pwd/proj 命令保留在主服务器的 /pathc/proj/hooks 中/post-commit 文件位于文件末尾。我收到上述错误，但如果我在主服务器上的 shell 提示符下运行此命令，它可以正常工作。我该如何解决这个问题？
I want to check out from a mirror, but commit to the master without svn sw , is it possible?
With svn sw --relocate I can do this, but I want to automatically change from slave to master during commits. How svn checkout will work ( Process) Can any one explain this.
Can't I set the target IP or master IP of the slave server during check-out? Is there any script?
I am trying to sync data from master server itself but I am getting the following error:
Warning: post-commit hook failed (exit code 255) with output: Host key verification failed.
I kept slave's svnsync sync file:///pwd/proj command in master's /pathc/proj/hooks/post-commit file at the end of the file. I am getting the above error, but if I run this command in a shell prompt on master server it works fine. How can I resolve this?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
SVNMasterURI 似乎是这里的关键字。
我只见过有人这样做。由于还没有其他答案，我想，在这里引用我的笔记总比没有好。不过，您应该将它们作为进一步研究的起点，而不是作为该主题的最终真相。
在镜像上使用 apache，当然还可以使用 http(s) 从客户端访问存储库。
配置 Apache 将所有写入命令 (=commit) 重定向到主 svn 服务器。读取命令（=更新等）仍然在本地提供。
看来您不能在具有此设置的镜像上使用 AuthzSVNAccessFile，否则提交到主服务器据说不起作用。
在我看到的示例中，更改了以下文件： /etc/apache2/mods-enabled/dav_svn.conf
注意：“ldap”和“external”只是作为示例，您可以使用不同的身份验证机制进行读取和写入（ = 镜子和主人）。在此示例中，在镜像上使用 ldap 来执行读取命令，在主服务器上使用 external。进一步的ldap配置和ExternalAuth配置这里省略。
SVNMasterURI seems to be the keyword here.
I have only seen someone doing this. Since there is no other answer yet, it is better than nothing, I guess, to cite my notes here. You should use them as a starting point for further research, though, not as the final truth on the subject.
Use apache on the mirror and of course http(s) for acccesing the repository from your client.
Configure Apache to redirect all write commands (=commit) to the master svn server. Read commands (= update etc.) are still to be served locally.
It seems you cannot use AuthzSVNAccessFile on the mirror with this setup, or else commits to the master are said to be not working.
In the example I saw, the following file was changed: /etc/apache2/mods-enabled/dav_svn.conf
Note: "ldap" and "external" are just there as examples that you can use different auth mechanisms for read and write (= mirror and master). In this example, ldap was used on the mirror for read commands, external was used with the master. Further ldap configuration and ExternalAuth configuration are omitted here.