web commit from 127.0.0.1

master
joey 2006-07-07 19:38:35 +00:00
parent 42ffdb661c
commit 1cd1f073ff
4 changed files with 33 additions and 4 deletions

View File

@ -38,9 +38,10 @@ Some of ikiwiki's features:
unchanged by ikiwiki as it builds your wiki. So you can check in an image,
program, or other special file and link to it from your wiki pages.
* [[SubPage]]s
* [[SubPages|SubPage]]
Arbitrarily deep hierarchies of pages with fairly simple and useful [[SubPage/LinkingRules]]
Arbitrarily deep hierarchies of pages with fairly simple and useful
[[SubPage/LinkingRules]]
* [[blogging|blog]]
@ -135,6 +136,11 @@ Some of ikiwiki's features:
After rather a lot of fiddling, we think that ikiwiki correctly and fully
supports utf8 everywhere.
* [[serverless]] mode
Can be set up so that w3m can be used to browse a wiki and edit pages
without using a web server.
----
It also has some [[TODO]] items and [[Bugs]].

View File

@ -48,6 +48,8 @@ Bulleted list
*one
*one
hi, mom!
----
[[haiku hint="sandbox play"]]
@ -67,4 +69,4 @@ Bulleted list
This sandbox is also a [[blog]]!
[[inline pages="sandbox/*" rootpage="sandbox" show="5"]]
[[inline pages="sandbox/*" rootpage="sandbox" show="5"]]

View File

@ -0,0 +1,3 @@
It's possible to use all of ikiwiki's web features (page editing, etc) in
the `w3m` web browser without using a web server. `w3m` supports local CGI
scripts, and ikiwiki can be set up to run that way.

View File

@ -3,4 +3,22 @@ and $EDITOR. Browse around a wiki, select pages to edit and get dropped
right into the editor and have the page committed to svn automatically.
Less grandiosely, a simple command line util to add a new page would be
useful, especially if it made it easy to add blog entries to the wiki. I have a special purpose version of this in my [blog script](http://kitenet.net/~joey/code/bin.html).
useful, especially if it made it easy to add blog entries to the wiki. I
have a special purpose version of this in my [blog
script](http://kitenet.net/~joey/code/bin.html).
----
w3m's cgi mode requires that cgis be in /usr/lib/w3m/cgi-bin/, and the url
for it can be $LIB/script. This presents a problem, since a regular user
can't add an ikiwiki wrapper to there (nor should they). But,
/usr/lib/w3m/cgi-bin/ikiwiki could be a meta-wrapper, that is passed the
path to the real wrapper in PATH_INFO, validates it, and runs the real
wrapper. So:
<a href="file:///$LIB/ikiwiki.cgi/home/joey/.ikiwiki/wrappers/ikiwiki.cgi">
Validation is important, because we don't want just any html document
including an evil w3m cgi that gets unintentionally run. The validation I'm
thinking of is that the ikiwiki meta-wrapper only runs wrappers in
$HOME/.ikiwiki/wrappers/, which the user presumably controls.