[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2816: make sure tub.location and tub.port can be empty

[Tahoe-LAFS]

#2816: make sure tub.location and tub.port can be empty
--------------------------------+--------------------
     Reporter:  warner          |      Owner:  warner
         Type:  task            |     Status:  new
     Priority:  normal          |  Milestone:  1.12.0
    Component:  code-nodeadmin  |    Version:  1.11.0
   Resolution:                  |   Keywords:
Launchpad Bug:                  |
--------------------------------+--------------------

Comment (by warner):

 Note that the way to configure a client to not listen at all is to have
 this:

 {{{
 # disable listening
 [node]
 tub.port =
 tub.location =
 }}}

 But don't do it like this, because it won't do the right thing:

 {{{
 # doesn't work!
 [node]
 }}}

 or:

 {{{
 # doesn't work!
 [node]
 #tub.port =
 #tub.location =
 }}}

 (if they're missing entirely, then tub.location will autodetect, and
 tub.port will either read the `NODEDIR/client.port` file or allocate a new
 port)

 I'm willing to believe that we need a more obvious "disabled" syntax here.
 Maybe something like:

 {{{
 # possible alternate syntax
 [node]
 tub.port = none
 tub.location = none
 }}}

 but it's a bit awkward, given that tub.port is usually an endpoint string
 (so it's fairly open-ended), and tub.location is a comma-separated hints
 string (also open-ended). We could steal a few names from those namespaces
 to mean "disabled", but there's always going to be a bit of tension
 /syntax-violating going on.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2816#comment:4>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage