aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorspalax <spalax@web>2014-05-09 16:33:12 -0400
committeradmin <admin@branchable.com>2014-05-09 16:33:12 -0400
commit54d47eb26ae41ff23932b9c0e3f15e698cb56ada (patch)
treec75246b3f70732f243045e017591f81afee29469 /doc
parentfc24df96c10b804d3022eb92caf687729921adbb (diff)
downloadikiwiki-54d47eb26ae41ff23932b9c0e3f15e698cb56ada.tar
ikiwiki-54d47eb26ae41ff23932b9c0e3f15e698cb56ada.tar.gz
Details about gitolite integration
Diffstat (limited to 'doc')
-rw-r--r--doc/tips/Hosting_Ikiwiki_and_master_git_repository_on_different_machines.mdwn4
1 files 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).