tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

Change intrododucer to one controlled by PRabahy. PRabahy will now be in charge of maintaining reasonable introducer uptime (no guarantees). 

[Imported from Trac: page TestGrid, version 77]
PRabahy 2013-02-04 02:33:09 +00:00
parent d7a344cb43
commit 430d897f1a
1 changed files with 10 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
TestGrid.md

@ -12,18 +12,16 @@ The pubgrid also has two critical non-goals
* The pubgrid is not intended to provide large-scale storage, and it is not intended to be reliable. Don't store any data in the pubgrid if losing it would cause trouble.
* Don't view the pubgrid as a free hundreds-of-MB backup service.
Note that the introducer furl has changed recently (as of November 2012).
Note that the introducer furl has changed recently (as of Feb. 2013).
## Cautions
The canonical way to access Tahoe-LAFS grids is to run your own client node. Having one's own node is necessary for the data that should remain private (plaintext, capabilities) to remain on your computers, while storage nodes provide storage of ciphertext. However, writing to the publically-writeable test directory (below) means that others can see and change your files.
Do not confuse the security properties one gets with tahoe when running a client node with how the public web interface (now disabled) used to behave.
## Publically writeable test directory
URI:DIR2:ctmtx2awdo4xt77x5xxaz6nyxm:n5t546ddvd6xlv4v6se6sjympbdbvo7orwizuzl42urm73sxazqa . Note that anyone may view and change this data.
URI:DIR2:fluzmpvcsdhtekvrolspclokya:xzlolymgub6pl6gcsy3v5y76nduv6d6z2o5g2xawsqdyhzwgzpba . Note that anyone may view and change this data.
## How To Connect To The Public Test Grid
@ -31,7 +29,7 @@ The test grid is subject to being updated at random times, so compatibility
is likely to break without notice. Also note that many upgrades require all
files and directories to be flushed, especially as storage formats change.
The test grid is currently running an 1.0.0-compatible release (allmydata-tahoe: 1.8.2) (see "My versions" on the welcome page for the current version of the web gateway server).
The test grid is currently running an 1.0.0-compatible release (allmydata-tahoe: 1.9.2) (see "My versions" on the welcome page for the current version of the web gateway server).
Set up the code according to source:docs/quickstart.rst and source:docs/running.rst. This creates a client node in the `.tahoe` subdirectory of your home directory. Edit the following lines into the `.tahoe/tahoe.cfg` file:
@ -45,7 +43,7 @@ Set up the code according to source:docs/quickstart.rst and source:docs/running.
<tr>
<td>
client<br>
introducer.furl = <b><i>pb://u7w4hdwgw5lfsuw7cnovh4jcoyvlne7o@128.59.153.44:51644/introducer</i></b><br>
introducer.furl = <b><i>pb://hckqqn4vq5ggzuukfztpuu4wykwefa6d@publictestgrid.dnsd.info:50213/introducer</i></b><br>
</td>
</tr>
</table>
@ -55,7 +53,7 @@ Set up the code according to source:docs/quickstart.rst and source:docs/running.
Then run `bin/tahoe start`.
We created a shared public directory: feel free to use it for experimentation -- once your node is up and listening on port 3456, [this URL](http://127.0.0.1:3456/uri/URI:DIR2:ctmtx2awdo4xt77x5xxaz6nyxm:n5t546ddvd6xlv4v6se6sjympbdbvo7orwizuzl42urm73sxazqa/) should give you access to that directory.
We created a shared public directory: feel free to use it for experimentation -- once your node is up and listening on port 3456, [this URL](http://127.0.0.1:3456/uri/URI:DIR2:fluzmpvcsdhtekvrolspclokya:xzlolymgub6pl6gcsy3v5y76nduv6d6z2o5g2xawsqdyhzwgzpba/) should give you access to that directory.
## Social Norms
@ -73,4 +71,8 @@ Suggested server setup:
## Other Public Volunteer Grids
* [VolunteerGrid2](http://www.bigpig.org/)
* [VolunteerGrid2](http://www.bigpig.org/)
## Contact Info
If the pubgrid introducer appears to be down, either send an email to the tahoe-dev mailing list or contact PRab on irc://freenode/tahoe-lafs