aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorhttp://christian.amsuess.com/chrysn <http://christian.amsuess.com/chrysn@web>2014-01-30 11:24:34 -0400
committeradmin <admin@branchable.com>2014-01-30 11:24:34 -0400
commitd33a651051ef03e1d61fde71113c873972d258b4 (patch)
tree0a129b487a6354ed4225c315c19f54394b763955
parentb3c99d9368d11125779ebc7e6537c7967b2112bc (diff)
downloadikiwiki-d33a651051ef03e1d61fde71113c873972d258b4.tar
ikiwiki-d33a651051ef03e1d61fde71113c873972d258b4.tar.gz
on ikiwiki with gitolite
-rw-r--r--doc/tips/Hosting_Ikiwiki_and_master_git_repository_on_different_machines.mdwn5
1 files changed, 5 insertions, 0 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 baf7ac6c8..35feacb71 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
@@ -149,3 +149,8 @@ the IkiWiki machine, and here is the deadlock. Explanations of the command:
- *Using [[gitolite|https://github.com/sitaramc/gitolite]] to manage
repositories on the git machine* Simply replace the manipulations of git on
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 ...`
+
+ 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).