[tahoe-lafs-trac-stream] [tahoe-lafs] #1385: stop respecting the pre-v1.3.0 configuration files

[tahoe-lafs]

#1385: stop respecting the pre-v1.3.0 configuration files
-------------------------+-------------------------------------------------
     Reporter:  zooko    |      Owner:
         Type:           |     Status:  new
  enhancement            |  Milestone:  1.9.0
     Priority:  minor    |    Version:  1.8.2
    Component:  code-    |   Keywords:  docs configuration defaults
  nodeadmin              |  usability
   Resolution:           |
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by warner):

 I'd like some sort of warning in a release or two, but Zooko says he's
 writing code to detect-and-complain-about the old files, which I'm happy
 with as long as we have a plan to remove it eventually (probably around
 the 2.0 timeframe) (so we don't accumulate old cruft forever). Note that
 it'd probably be sufficient to do a fatal complaint about the lack of a
 {{{tahoe.cfg}}}, because the nodes that were configured with individual
 files probably won't have one, and that sort of complaint could be kept
 around forever.

 I'm ok with regressing on multiple-log-gatherers until Foolscap has an API
 to handle that. I'd prefer the whitespace-separated tahoe.cfg key over
 having a separate file with a funny name.

 (note that part of the reason for having discrete files for things like
 log-gatherers was to make it easy to set up or modify a whole bunch of
 Allmydata servers with a batch of {{{scp}}} commands: just stuff the
 {{{log-gatherer.furl}}} file into all of them and then bounce them all. To
 do that with {{{tahoe.cfg}}} requires editing files, so needs more complex
 tooling. But I don't think this is an important feature these days, and I
 prefer the simplicity of a single config file).

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1385#comment:7>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage