[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2833: Enable using values from environment variables from tahoe.cfg

[Tahoe-LAFS]

#2833: Enable using values from environment variables from tahoe.cfg
-----------------------------+-----------------------------------
     Reporter:  amontero     |      Owner:
         Type:  enhancement  |     Status:  closed
     Priority:  normal       |  Milestone:  undecided
    Component:  unknown      |    Version:  1.11.0
   Resolution:  wontfix      |   Keywords:  environment variables
Launchpad Bug:               |
-----------------------------+-----------------------------------
Changes (by exarkun):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 A node configuration is a pretty complex structure.  Representing it
 completely in environment variables seems likely to me to be something of
 a mess.

 There are also parts of the configuration which are sensitive and should
 be kept secret and environment variables are not a way to accomplish that.

 I'd suggest that for things like Docker images, the image itself should be
 somewhat tailored to a specific use and should accept *some* configuration
 in environment variables - then turn around and write a tahoe.cfg and
 start up a node pointed at that.

 That is, the Tahoe node process itself should not directly support any
 configuration as environment variables.

 An alternative to this would be for Tahoe to expose an API that allows
 full control over configuration.  Then, a bare-bones node could be started
 up and then configured with API calls containing arbitrary configuration.

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