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

New Issue

warner · 2016-09-10T02:31:32Z

warner commented

2016-09-10 02:31:32 +00:00

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

warner added the

labels 2016-09-10 02:31:32 +00:00

warner added this to the 1.12.0 milestone 2016-09-10 02:31:32 +00:00

warner self-assigned this 2016-09-10 02:31:32 +00:00

warner commented

2016-09-10 02:33:37 +00:00

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.

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 commented

2016-09-13 14:04:53 +00:00

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.

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 commented

2016-09-14 11:47:47 +00:00

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

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

Brian Warner <warner@lothar.com> commented

2016-09-14 19:46:35 +00:00

In 8a4dc21/trunk:

Merge PR 344 from david415/2877.doc_cli_where_opts.0

closes tahoe-lafs/tahoe-lafs#344

refs ticket:2827

In [8a4dc21/trunk](/tahoe-lafs/trac-2024-07-25/commit/8a4dc213f9f154861fc889a118c7402682eab0f3): ``` Merge PR 344 from david415/2877.doc_cli_where_opts.0 closes tahoe-lafs/tahoe-lafs#344 refs ticket:2827 ```

warner commented

2016-09-14 20:13:37 +00:00

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

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

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 commented

2016-09-15 00:10:10 +00:00

[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.

[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.

warner added the

fixed

label 2016-09-15 00:10:10 +00:00

warner closed this issue

2016-09-15 00:10:10 +00:00

Sign in to join this conversation.