aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoey Hess <joey@kodama.kitenet.net>2008-06-04 11:29:07 -0400
committerJoey Hess <joey@kodama.kitenet.net>2008-06-04 11:29:07 -0400
commit325fc9d8d03676eab1fdc78e6b65155af0ebcc2b (patch)
tree7b3370077e363fe3d67afc324d3133ab05f12056
parentbf9829352b85e358f33061e65ece5d5515780840 (diff)
downloadikiwiki-325fc9d8d03676eab1fdc78e6b65155af0ebcc2b.tar
ikiwiki-325fc9d8d03676eab1fdc78e6b65155af0ebcc2b.tar.gz
done
-rw-r--r--doc/todo/CGI_method_to_pullrefresh.mdwn2
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/todo/CGI_method_to_pullrefresh.mdwn b/doc/todo/CGI_method_to_pullrefresh.mdwn
index 89b7491c0..6b5824bd3 100644
--- a/doc/todo/CGI_method_to_pullrefresh.mdwn
+++ b/doc/todo/CGI_method_to_pullrefresh.mdwn
@@ -3,3 +3,5 @@
In some situations, it makes sense to have the repository in use by ikiwiki reside on a different machine. In that case, one could juggle SSH keys for the `post-update` hook. A better way may be to provide a different `do` parameter handler for the CGI, which would pull new commits to the working clone and refresh the wiki. Then, the remote `post-update` hook could just `wget` that URL. To prevent simple DoS attacks, one might assign a simple password.
[[tag wishlist]]
+
+> [[done]] via the pinger and pingee plugins --[[Joey]]