[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2821: make "tahoe create-client --hide-ip" fail if txtorcon/txi2p are not installed

[Tahoe-LAFS]

#2821: make "tahoe create-client --hide-ip" fail if txtorcon/txi2p are not
installed
----------------------------+------------------------
 Reporter:  warner          |          Owner:
     Type:  enhancement     |         Status:  new
 Priority:  normal          |      Milestone:  1.12.0
Component:  code-nodeadmin  |        Version:  1.11.0
 Keywords:  anonymity tor   |  Launchpad Bug:
----------------------------+------------------------
 This would speed up the interactive discovery process when a node admin
 tries to set up a tor/i2p -based node. Instead of:

 * `pip install tahoe-lafs`
 * `tahoe create-client --hide-ip`
 * edit tahoe.cfg
 * `tahoe start`
 * error: txtorcon not installed
 * `pip install tahoe-lafs[tor]`
 * `tahoe start`
 * no error, but welcome page shows connection not established
 * oops, `apt-get install tor`
 * `tahoe restart`
 * ok

 we could make it:

 * `pip install tahoe-lafs`
 * `tahoe create-client --hide-ip`
 * error: txtorcon not installed
 * `pip install tahoe-lafs[tor]`
 * `tahoe create-client --hide-ip`
 * edit tahoe.cfg
 * `tahoe start`
 * no error, but welcome page shows connection not established
 * oops, `apt-get install tor`
 * `tahoe restart`
 * ok

 And then maybe we can detect that there's no tor daemon available too
 (perhaps create-client could try to establish a connection to a tor server
 we run on tahoe-lafs.org, or torproject.org, or something), and cut down a
 few more steps.

 I think #2820 and having `create-client` disable the tub listeners would
 remove the need for the `edit tahoe.cfg` step.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2821>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage