Changes between Version 33 and Version 34 of WikiStart

Timestamp:

2011-01-09 07:11:07 (14 years ago)

Author:

zooko

Comment:

a few tweaks to the docs

WikiStart

@@ -2 +2 @@
 
 [http://www.tiddlywiki.com TiddlyWiki] is a client-side wiki written purely in HTML/CSS and !JavaScript.
-[http://tahoe-lafs.org Tahoe-LAFS] is a decentralized, secure storage grid.  These go together like chocolate and peanut butter!  We call the result an Unhosted Wiki, or !UnWiki.
+[http://tahoe-lafs.org Tahoe-LAFS] is a decentralized, secure storage grid.  These go together like chocolate and peanut butter!  We call the result an ''Unhosted Wiki''.
 
-For a hands on introduction here is an [http://pubgrid.tahoe-lafs.org/uri/URI%3ADIR2%3Afx7qhfvfrrm7um327ntkjwfu3m%3Atynsxdcwm5imqwqmdrv7wvwj2jupjlyt5pgnu4nmmct6vledgw2a/wiki.html Unhosted Wiki] you can play with. Follow the link, edit the !UnWiki, and click "Save Changes"! :-)
+For a hands on introduction here is an [http://pubgrid.tahoe-lafs.org/uri/URI%3ADIR2%3Afx7qhfvfrrm7um327ntkjwfu3m%3Atynsxdcwm5imqwqmdrv7wvwj2jupjlyt5pgnu4nmmct6vledgw2a/wiki.html Unhosted Wiki] you can play with. Follow the link, edit the Unhosted Wiki, and click "Save Changes"! :-)
 
-== To Build a Tahoe-Ready !TiddlyWiki (Unhosted Wiki) == 
+== To Build a Tahoe-LAFS-Ready !TiddlyWiki (Unhosted Wiki) == 
 
-=== You'll need tahoe: ===
+=== You'll need tahoe-lafs: ===
 
-Set up a tahoe client on a '''secure''' machine following the {{{"}}}[http://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/quickstart.html quickstart]{{{"}}} and {{{"}}}[http://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/running.html#Doing running]{{{"}}} instructions.
+Set up a tahoe-lafs web gateway on a '''secure''' machine which is controlled only by you following the {{{"}}}[http://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/quickstart.html quickstart]{{{"}}} and {{{"}}}[http://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/running.html#Doing running]{{{"}}} instructions.
 
-Now that you have a tahoe client running (on a '''secure''' platform, like your laptop) the next step is to pu''blish'' the tiddlywiki, on the  grid. To do this...
+Now that you have a tahoe-lafs gateway running (on a machine under your own control, like your laptop) the next step is to pu''blish'' the tiddlywiki, through the gateway, onto the tahoe-lafs grid. To do this...
 
-=== You'll need a customized tiddlywiki: ===
+=== You'll need a tiddlywiki with a couple of plugins: ===
 
-Use wget to get the customized tiddlywiki:
+Use wget to get a copy of an empty tiddlywiki with the ''HTTPSavingPlugin'' and ''TahoePlugin'' already installed:
 
 {{{wget http://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 pu''blish'' the tiddlwiki to the grid: ==
@@ -24 +26 @@
 Use the CLI described under the [http://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/running.html#Doing running] documentation.  
 
-You need a tahoe directory to publish the tiddlywiki on.  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. 
+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 ==
@@ -37 +39 @@
 {{{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 access the tiddlywiki. Since this is the case I recommend the following single step publication...
+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`}}}
+{{{tahoe cp wiki.html `tahoe mkdir | tee WRITECAPABILITY.txt`}}}
 
 You can now access your Unhosted Wiki via:
 
-{{{http://localhost:3456/WRITECAPABILITY/wiki.html}}}
-
+{{{http://localhost:3456/`cat WRITECAPABILITY.txt`/wiki.html}}}