# Similar and related tips and problems
+- [[tips/distributed_wikis]] References different way of distributing wikis (including this one).
- [[http://www.icanttype.org/blog/ikiwiki_git_remote_repo/]] Similar to what I
am describing, excepted that you must be able to connect to the machine
hosting Ikiwiki using ssh.
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*.
## Going further
- *Web server on a third machine* It should be possible to use a third machine
- to host the web server. A hook might be used to export the rendered wiki on
- this server, or use a nfs repository as the destination repository of
- ikiwiki. However, allowing web modifications (using CGI) might be tricky…
+ to host the web server, using [[this documentation|tips/Git_repository_and_web_server_on_different_hosts/]].
- *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 ...`
+ `[ 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).