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.
- Timestamp:
-
2011-01-10 07:34:07 (14 years ago)
- Author:
-
zooko
- Comment:
-
add explanation of how to share a read-only link
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v40
|
v41
|
|
14 | 14 | If you do not have access to a different grid, then use the test grid. This is accomplished by following [http://tahoe-lafs.org/trac/tahoe-lafs/wiki/TestGrid these] instructions. |
15 | 15 | |
16 | | 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... |
| 16 | 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 your personal gateway, onto the tahoe-lafs grid. The rest of these instructions will assume that the URL for your personal gateway is {{{http://localhost:3456/}}}. |
17 | 17 | |
18 | 18 | === You'll need a tiddlywiki with a couple of plugins: === |
… |
… |
|
24 | 24 | (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.) |
25 | 25 | |
26 | | == You'll need to pu''blish'' the tiddlwiki to the grid: == |
| 26 | == You'll need to pu''blish'' the tiddlywiki to the grid: == |
27 | 27 | |
28 | 28 | Use the CLI described under the [http://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/running.html#Doing running] documentation. |
… |
… |
|
30 | 30 | 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. |
31 | 31 | |
32 | | == Stepwise == |
| 32 | === Stepwise === |
33 | 33 | One, running: |
34 | 34 | |
… |
… |
|
43 | 43 | 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... |
44 | 44 | |
45 | | == Combined: == |
| 45 | === Combined: === |
46 | 46 | |
47 | 47 | {{{tahoe cp wiki.html `tahoe mkdir | tee WRITECAPABILITY.txt`}}} |
… |
… |
|
50 | 50 | |
51 | 51 | {{{echo http://localhost:3456/uri/`cat WRITECAPABILITY.txt`/wiki.html}}} |
| 52 | |
| 53 | (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}}} |
| 54 | |
| 55 | == You may want to share a read-only view of the tiddlywiki == |
| 56 | |
| 57 | To get the read-only cap to the same directory, run: |
| 58 | |
| 59 | {{{wget http://localhost:3456/uri/`cat WRITECAPABILITY.txt`?t=json}}} |
| 60 | |
| 61 | and inspect the resulting file for the ''first'' occurrence of {{{ro_uri}}}. Put that string into a file named {{{READONLYCAPABILITY.txt}}}. |
| 62 | |
| 63 | Now share a URL like this: |
| 64 | |
| 65 | {{{http://insecure.tahoe-lafs.org/uri/`cat READONLYCAPABILITY.txt`/wiki.html}}} |