From 54d47eb26ae41ff23932b9c0e3f15e698cb56ada Mon Sep 17 00:00:00 2001 From: spalax Date: Fri, 9 May 2014 16:33:12 -0400 Subject: [PATCH] Details about gitolite integration --- ...iwiki_and_master_git_repository_on_different_machines.mdwn | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/tips/Hosting_Ikiwiki_and_master_git_repository_on_different_machines.mdwn b/doc/tips/Hosting_Ikiwiki_and_master_git_repository_on_different_machines.mdwn index af4438bd5..6bbaf3e6e 100644 --- a/doc/tips/Hosting_Ikiwiki_and_master_git_repository_on_different_machines.mdwn +++ b/doc/tips/Hosting_Ikiwiki_and_master_git_repository_on_different_machines.mdwn @@ -150,6 +150,6 @@ the IkiWiki machine, and here is the deadlock. Explanations of the command: the git machine by the corresponding manipulations using gitolite. * With gitolite, you can use this line in a `post-update` hook: - `[ x"$GL_USER" = x"`*`gitolite-user`*`" ] || wget ...` + `[ x"$GL_USER" = x"`*`gitolite-user`*`" ] || wget ...` where *gitolite-user* is the name of the public key registered through gitolite. - thus, you filter out precisely the events that originate from the server-to-be-pinged, no matter what the commit id says. (For example, if you push commits you created on a local CGI ikiwiki, they'd be called '@web' as well). + Thus, you filter out precisely the events that originate from the server-to-be-pinged, no matter what the commit id says. (For example, if you push commits you created on a local CGI ikiwiki, they'd be called '@web' as well).