X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/038f35ed6b5ea5f5055361ad3c0173d1595276de..32a3d8efaa64077892f5124982174d5985254935:/doc/tips/Hosting_Ikiwiki_and_master_git_repository_on_different_machines.mdwn

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..6af4f9619 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
@@ -1,4 +1,5 @@
 [[!meta title="Hosting Ikiwiki with a master git repository on a remote machine"]]
+[[!meta date="2013-07-22 16:38:20 -0400"]]
 
 This tutorial explains how to set up a wiki such that:
 
@@ -38,6 +39,8 @@ it on a remote machine, and tell Ikiwiki to use it instead of its local one. We
 will also ensure that the wiki is rendered whenever a commit is done to the git
 repository.
 
+[[!img separate-web-git-servers.svg size=400x]]
+
 # Conventions
 
 - We are building a wiki called *SITE*.
@@ -72,7 +75,7 @@ repository.
 ## Configuring the wiki on the wiki machine so that it uses the repository of the git machine
 
 - Configure ssh so that it uses the ssh key `id_SITE` to connect to the git
-  michine: add the following lines to file `~/.ssh/config` on the ikiwiki
+  machine: add the following lines to file `~/.ssh/config` on the ikiwiki
   machine:
 
         Host server.name.of.the.git.machine
@@ -150,6 +153,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).