document new --location/--port / --hostname / --listen options

[warner]

We need docs for the new #2773 and #2490 options.

[warner]

I'd like a docs/servers.rst with an explanation of the various network scenarios you might encounter (public-IP, firewall with port forwarding, unreachable but using an Onion service, etc). For each one, it should explain what you need to collect or allocate (hostnames, port numbers), what arguments to use when building the node, and how to perform any extra configuration.

This would also be a good place to point at the server-over-tor/i2p docs.

[dawuud]

ok i started to write about these different network configuration scenarios here:

​https://github.com/david415/tahoe-lafs/tree/2827.doc_cli_where_opts.0

while writing it i realized we really should make a client ipv6 handler then we can tell users how to configure ipv6-only storage nodes... no NAT penetration needed.

[dawuud]

made a PR for your review: ​https://github.com/tahoe-lafs/tahoe-lafs/pull/344

[Brian Warner <warner@…>]

In 8a4dc21/trunk:

Merge PR 344 from david415/2877.doc_cli_where_opts.0

closes tahoe-lafs/tahoe-lafs#344

refs ticket:2827

[warner]

I pushed some more docs in [d69757e]. I'm happy with --port/--location/--hostname now.

Next step is to implement --listen and document it.

[warner]

[02ba2a05] added docs for --listen. We haven't enabled --listen=tor yet, but the docs are in place for it, so I think we can close this ticket now.