From 6d669029bdf291361f0b38de645355324c644fce Mon Sep 17 00:00:00 2001
From: david-sarah
If the Tahoe-LAFS bin
directory is not on your PATH, then
+ in all the command lines below, specify the full path to bin/tahoe
.
To construct a client node, run
- "path-to-the-tahoe-bin-directory/tahoe
- create-client
", which will create ~/.tahoe
to be the
+ "tahoe create-client
", which will create ~/.tahoe
to be the
node's base directory. Acquire a copy of the introducer.furl
from the introducer and put it into this directory, then use
- "path-to-the-tahoe-bin-directory/tahoe
- run
". After that, the node should be off and running. The first
+ "tahoe run
". After that, the node should be off and running. The first
thing it will do is connect to the introducer and get itself connected to
all other nodes on the grid. By default, a node will serve as a storage
node, meaning that it offers its disk space to other nodes. To configure
other behavior, see configuration.txt.
To construct an introducer, create a new base directory for it (the name
of the directory is up to you), cd
into it, and run
- "path-to-the-tahoe-bin-directory/tahoe
- create-introducer .
". Now run the introducer using
+ "tahoe create-introducer .
". Now run the introducer using
"tahoe start .
". After it starts, it will write a file named
introducer.furl
in that base directory. This file contains the
URL the other nodes must use in order to connect to this introducer.
The "tahoe run
" command above
will run the node in the foreground. On Unix, you can run it in the background
instead by using the "tahoe start
" command.
To stop a node started in this way, use "tahoe stop
".
tahoe --help
gives a summary of all commands.
See configuration.txt for more details about how to configure Tahoe-LAFS, including how to get other clients to connect to your node if it is behind a firewall or NAT device. -- 2.45.2