The Public Test Grid

This page is about the "Test Grid", which is also called the "pubgrid". The pubgrid has several purposes:

• to make it easier for people new to tahoe to begin to experiment
• to enable small-scale trial use of tahoe
• to help the tahoe community gain experience with grids of heterogenous servers without a pre-existing social organization

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.

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, the pubgrid has a publically-accessible gateway; using this means plaintext of files and capabilities are exposed on the Internet. Even worse, writing to the publically-writable 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 behaves.

Live Demo

​the publically writeable directory through pubgrid.tahoe-lafs.org. Note that anyone may view and change this data.

Here is ​the welcome page which has a list of connected storage nodes, recent uploads and downloads, and performance statistics.

How To Connect To The Public Test Grid

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.0) (see "My versions" on the welcome page for the current version of the web gateway server).

After setting up the code according to ​docs/quickstart.html, edit the following lines into its tahoe.cfg file:

[node] nickname = Another nickname than "None"

[client] introducer.furl = pb://tin57bdenwkigkujmh6rwgztcoh7ya7t@pubgrid.tahoe-lafs.org:50528/introducer helper.furl = pb://sp26qyqclbwjv6lgqdxik5lfdlxrkpnz@skulls.nodes.soultcer.com:44519/io4e5utfosaxibnm7nk6viqjj6i4yd2g stats_gatherer.furl = pb://cmmth6b3lsj2orir3u5yqwwae7xfmxxq@pubgrid.tahoe-lafs.org:51424/jdoyd3kke4zqkmmvlhveb57xsw623kh5

Then run 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 should give you access to that directory.

Social Norms

By running a client node, you can store data in the pubgrid. The storage is provided by people who run storage nodes, and they share disk space and network capacity as a courtesy to the tahoe community in order to help newcomers and promote experimentation.

Norms for the pubgrid are similar to those for some private grids:

• If you are just trying out tahoe and not contributing a server, only store a small amount of data, perhaps 1-20 MB. This is perfectly fine; people contribute resources so that new people can experiment.
• If you are a more serious pubgrid participant, contribute some amount of disk space and run stable servers with public IP addresses (so that clients can connect to them). Then, only store about half as much in shares (3.3x expansion for 3/10 encoding) as you provide in storage.
• People storing more than the above small amounts of data, as well as those running servers should be on the ​tahoe-dev mailing list.

Suggested server setup:

• Enable expiration with 1-month lease maximums on your node, to keep it from just filling up.