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

new introducer furl 

[Imported from Trac: page TestGrid, version 73]
davidsarah 2012-11-26 02:02:32 +00:00
parent 928250d5e2
commit 13e9a8c1b9
1 changed files with 4 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
TestGrid.md

@ -1,9 +1,4 @@
The pubgrid was temporarily disabled on 2011-07-24. See <http://tahoe-lafs.org/pipermail/tahoe-dev/2011-July/006572.html>.
The introducer was later reenabled, and many storage servers are still connected, but there will be no public gateway.
The introducer appears to be down as of 2012-10-24.
# The Public Test Grid # The Public Test Grid
This page is about the "Test Grid", which is also called the "pubgrid". The pubgrid has several purposes: This page is about the "Test Grid", which is also called the "pubgrid". The pubgrid has several purposes:
@ -17,6 +12,9 @@ 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. * 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. * Don't view the pubgrid as a free hundreds-of-MB backup service.
There is no public gateway; that was [disabled on 2011-07-24](http://tahoe-lafs.org/pipermail/tahoe-dev/2011-July/006572.html). Note that the introducer furl has changed recently (as of November 2012).
## Cautions ## 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. 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.
@ -47,8 +45,7 @@ Set up the code according to source:docs/quickstart.rst and source:docs/running.
<tr> <tr>
<td> <td>
client<br> client<br>
introducer.furl = <b><i>pb://tin57bdenwkigkujmh6rwgztcoh7ya7t@pubgrid.tahoe-lafs.org:50528/introducer</i></b><br> introducer.furl = <b><i>pb://u7w4hdwgw5lfsuw7cnovh4jcoyvlne7o@128.59.153.44:51644/introducer</i></b><br>
stats_gatherer.furl = <b><i>pb://cmmth6b3lsj2orir3u5yqwwae7xfmxxq@pubgrid.tahoe-lafs.org:51424/jdoyd3kke4zqkmmvlhveb57xsw623kh5</i></b>
</td> </td>
</tr> </tr>
</table> </table>