mirror of
https://github.com/tahoe-lafs/tahoe-lafs.git
synced 2025-02-19 09:16:39 +00:00
Use "tahoe run"
This commit is contained in:
parent
914e7ac013
commit
20dd4d55ad
@ -273,7 +273,7 @@ Then, do the following:
|
|||||||
[connections]
|
[connections]
|
||||||
tcp = tor
|
tcp = tor
|
||||||
|
|
||||||
* Launch the Tahoe server with ``tahoe start $NODEDIR``
|
* Launch the Tahoe server with ``tahoe run $NODEDIR``
|
||||||
|
|
||||||
The ``tub.port`` section will cause the Tahoe server to listen on PORT, but
|
The ``tub.port`` section will cause the Tahoe server to listen on PORT, but
|
||||||
bind the listening socket to the loopback interface, which is not reachable
|
bind the listening socket to the loopback interface, which is not reachable
|
||||||
@ -435,4 +435,3 @@ It is therefore important that your I2P router is sharing bandwidth with other
|
|||||||
routers, so that you can give back as you use I2P. This will never impair the
|
routers, so that you can give back as you use I2P. This will never impair the
|
||||||
performance of your Tahoe-LAFS node, because your I2P router will always
|
performance of your Tahoe-LAFS node, because your I2P router will always
|
||||||
prioritize your own traffic.
|
prioritize your own traffic.
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user