wiki:WikiStart
close Warning: Can't synchronize with repository "(default)" (Unsupported version control system "darcs": Can't find an appropriate component, maybe the corresponding plugin was not enabled? ). Look in the Trac log for more information.

TiddlyWiki on Tahoe-Lafs

TiddlyWiki is a client-side wiki written purely in HTML/CSS and JavaScript. Tahoe-LAFS is a decentralized, secure storage grid. These go together like chocolate and peanut butter! We call the result a Server-Independent Wiki.

To Build a Tahoe-LAFS-Ready TiddlyWiki (Server-Independent Wiki)

You'll need tahoe-lafs:

Set up a tahoe-lafs web gateway on a secure machine which is controlled only by you following the "quickstart" and "running" instructions.

Now that you have a tahoe-lafs gateway running (on a machine under your own control, like your laptop) the next step is to publish the tiddlywiki, through your personal gateway, onto the tahoe-lafs grid.

You'll need a tiddlywiki with a couple of plugins:

Use wget to get a copy of an empty tiddlywiki with the HTTPSavingPlugin and TahoePlugin already installed (get them from https://tahoe-lafs.org/source/tiddly_on_tahoe/trunk/tahoe_tiddly/):

wget https://tahoe-lafs.org/source/tiddly_on_tahoe/trunk/tahoe_tiddly/wiki.html

(Note: starting with this empty file that comes preloaded with the plugins is just for convenience—if you already have a tiddlywiki document that you want to publish on a tahoe-lafs grid, you can simply add the HTTPSavingPlugin and TahoePlugin to your current file and then proceed with these instructions.)

You'll need to publish the tiddlywiki to the grid:

Use the CLI described in the "running" documentation.

You need a tahoe-lafs directory to put the tiddlywiki in. You could accomplish this by running the following steps in order, but it's preferable to put it together in a single command as demonstrated below.

Stepwise

One, running:

tahoe mkdir

generates such a directory and prints the write capability to it on sdout.

Two, running:

tahoe cp wiki.html write capability

publishes the wiki.html to the directory you created in the previous step. It's critical that the write capability is stored somewhere you can reliably get to, as it is the only way to get write-access the tiddlywiki. Since this is the case I recommend the following single step publication...

Combined:

tahoe cp wiki.html `tahoe mkdir | tee WRITECAPABILITY.txt`

You can now access your Unhosted Wiki by the URL that results from:

echo http://localhost:3456/uri/`cat WRITECAPABILITY.txt`/wiki.html

(That URL is assuming that your personal gateway is reachable at http://localhost:3456/. If your personal gateway is on a different port or a different host you'll have to adjust accordingly. Remember that if it is on a different host then someone else could sniff the connection from your local web browser to that gateway, unless you configure it to do https instead of http.)

You may want to share a read-only view of the tiddlywiki

If there is a publicly accessible gateway, you can give people a link to your tiddlywiki as served by that gateway.

Click on the link at the top of the tiddlywiki page which is labelled "Click here for a read-only view of this page ." to go to a read-only view of the wiki. Now edit the URL and replace localhost:3456 with http://$PUBLIC_GATEWAY. The result is a URL that you can share with someone to give them read-only access to your wiki.

Note that currently doing this also gives people the ability to upload their own files through that gateway to the grid. Ticket #587 is about making it possible to give someone download-only access to a gateway without necessarily giving them upload access.

Support

To report an issue, please use https://tahoe-lafs.org.

Last modified 10 years ago Last modified on 2011-12-12 07:53:46