| 33 | | 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). |
| 34 | | |
| 35 | | 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: |
| 36 | | |
| 37 | | || [node][[BR]]nickname = '''''Another nickname than "None"''''' || |
| 38 | | || [client][[BR]]introducer.furl = '''''pb://hckqqn4vq5ggzuukfztpuu4wykwefa6d@publictestgrid.twilightparadox.com:50213,publictestgrid.lukas-pirl.de:50213,publictestgrid.e271.net:50213,68.62.95.247:50213/introducer''''' || |
| 39 | | |
| 40 | | Then run {{{bin/tahoe start}}}. |
| 41 | | |
| 42 | | == Publicly writable test directory == |
| 43 | | |
| 44 | | We created a shared public directory: feel free to use it for experimentation -- once your node is up and listening on port 3456, [http://127.0.0.1:3456/uri/URI%3ADIR2%3Addg5n76x6stjb35psrcn7i3ytu%3Aetbtnftlaeylm4gmi7mxzq6pg2ntgra7dyjeronyoo4pvkgtttqa/ this URL] should give you access to that directory. |
| 45 | | |
| 46 | | URI:DIR2:ddg5n76x6stjb35psrcn7i3ytu:etbtnftlaeylm4gmi7mxzq6pg2ntgra7dyjeronyoo4pvkgtttqa . Note that anyone may view and change this data. |
| | 19 | The introducer fURL for the testgrid is `pb://fodk4doc64febdoxke3a4ddfyanz7ajd@tcp:testgrid.tahoe-lafs.org:5000/el4fo3rm2h22cnilukmjqzyopdgqxrd2`. |
| 54 | | * 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. |
| 55 | | * 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. |
| 56 | | * People storing more than the above small amounts of data, as well as those running servers should be on the [http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev tahoe-dev mailing list]. |
| | 29 | * If you are just trying out tahoe and not contributing a server, only store a small amount of data, perhaps 1-20 MB. |
| | 30 | This is perfectly fine; people contribute resources so that new people can experiment. |
| | 31 | * 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). |
| | 32 | Then, only store about half as much in shares (3.3x expansion for 3/10 encoding) as you provide in storage. |
| | 33 | * People storing more than the above small amounts of data, as well as those running servers should be on the [https://lists.tahoe-lafs.org/mailman/listinfo/tahoe-dev tahoe-dev mailing list]. |
| 64 | | The status of the pubgird can be checked by either looking at your nodes status page or checking http://stats.pingdom.com/cvvac5t8l4fv/1300061. That pingom page has been configured to verify that the introducers TCP port is reachable, but does not verify the status of any storage nodes. |
| 65 | | |
| 66 | | == History == |
| 67 | | |
| 68 | | A version of the pubgrid existed until some time in 2012, when the introducer was lost. In February of 2013, a new introducer was created, resulting in a change of furl. |
| 69 | | |
| 70 | | It is an interesting philosophical question as to whether the pubgrid with the new introducer is a different grid or not. If servers that had been connecting to the new introducer are repointed to the new introducer, it can be considered the same grid with a change of introducer, with the property that files from the old grid may still be accessible. |
| | 41 | The status of the pubgrid can be checked by either looking at your nodes status page. |
| | 42 | The community would welcome the contribution of a monitoring system for the grid. |
| 74 | | 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. |
| 75 | | |
| 76 | | == Other Public Volunteer Grids == |
| 77 | | |
| 78 | | * [http://www.bigpig.org/ VolunteerGrid2] '''(Discontinued)''' |
| | 46 | The canonical way to access Tahoe-LAFS grids is to run your own client node. |
| | 47 | Having one's own node is necessary for the data that should remain private (plaintext, capabilities) to remain on your computers, |
| | 48 | while storage nodes provide storage of ciphertext. |
