Subversion 挂钩问题
在这件事上花了太多时间。 我通过 Plesk 面板创建了子域 aaa.abc.com 我在终端中使用： svn checkout svn+ssh://abc.com/var/svn/base httpdocs 我有一个提交后挂钩，应该更新我的 httpdocs 文件夹中的文件。 它不起作用，但如果我使用终端，我可以使用“svn update”。
我确实有一个日志，它显示 ssh 错误。
该钩子用于更新多个子域，除了这个之外，所有子域都会更新。 我已经尝试了我能想到的所有权限组合...... 该钩子拥有：-rwxr-xr-x 1 root root 1118 Feb 24 04:44 post-commit httpdocs 拥有者： drwxrwx--- 8 svn svn 4096 Mar 11 10:05 httpdocs 我的日志：
Permission denied, please try again.
Permission denied, please try again.
Permission denied (publickey,gssapi-with-mic,password).
svn: Connection closed unexpectedly
谢谢
Spent way too much time on this one.
I created a subdomain aaa.abc.com through a Plesk Panel
I used: svn checkout svn+ssh://abc.com/var/svn/base httpdocs in the terminal
I have a post-commit hook that should update the files in my httpdocs folder.
It doesnt work , but it I use the terminal I can just use "svn update".
I do have a log and its showing an ssh error.
This hook is used to update several subdomains and they all update except this one.
I have tried every combination of permissions I could think of...
The hook is owned:-rwxr-xr-x 1 root root 1118 Feb 24 04:44 post-commit
The httpdocs is owned : drwxrwx--- 8 svn svn 4096 Mar 11 10:05 httpdocs
My Log:
Permission denied, please try again.
Permission denied, please try again.
Permission denied (publickey,gssapi-with-mic,password).
svn: Connection closed unexpectedly
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果你的 subversion 存储库和 httpdocs 文件夹位于同一服务器上（听起来像是），那么你应该使用文件机制来签出，而不是 svn+ssh 机制。使用上面的示例，您可以使用 svn checkout file:///var/svn/base 进行签出。然后，当您的提交后挂钩运行时，它会使用文件系统机制（不需要 ssh 身份验证）进行更新，并且一切正常。
If your subversion repository and your httpdocs folder are on the same server (and it sounds like they are), you should instead use the file mechanism for checkout instead of the svn+ssh mechanism. Using your example above, you would check out with
svn checkout file:///var/svn/base. Then when your post-commit hook runs it updates using the filesystem mechanism (which doesn't require ssh authentication), and everything Just Works.