+ cd ikiwiki-checkout
+ ikiwiki --setup ikiwiki.setup
+
+[And yes, if you're paying attention there, you just cloned from the
+bare repository into a directory that is also inside that same
+repository. I found this a neat place to hide away the
+clone-with-working-tree that ikiwiki needs to edit but that you
+shouldn't touch. If you think this is too creepy, you could put it
+anywhere else, and configure ikiwiki.setup to point to it there.]
+
+And finally, edit $gitrepo/hooks/post-update to call the new
+$gitrepo/hooks/ikiwiki-post-update program and also don't forget to
+actually enable the hook with:
+
+ chmod a+x $gitrepo/hooks/post-update
+
+Now, you're finally ready to go. You should be able to just start
+adding content under the src directory. You can give files a .mdwn
+extension to use markdown syntax to turn the contents into HTML. Here
+are some hints on doing that:
+
+ http://ikiwiki.info/helponformatting/
+
+To preview things locally, you can run "ikiwiki --setup
+ikiwiki.setup", (and ensure the destdir path exists on the local
+machine). When you're ready to publish to your server, it should be as
+simple as "git push".
+
+Problems
+========
+Here is a useful, (self explanatory), command-line options for
+debugging ikiwiki problems:
+
+ ikiwiki --verbose --setup ikiwiki.setup
+
+ ikiwiki --verbose --rebuild --setup ikiwiki.setup
+
+I've had occasions where the hook-based update fails for one reason or
+another, (for example, once when I moved the location of $gitrepo, but
+the compiled hook still had the old location). The basic recipe for
+unwedging things in this case was as simple as running the following
+on the server: