[tahoe-lafs-trac-stream] [Tahoe-LAFS] #467: allow the user to specify which servers a given gateway will use for uploads

[Tahoe-LAFS]

#467: allow the user to specify which servers a given gateway will use for
uploads
-------------------------+-------------------------------------------------
     Reporter:  warner   |      Owner:  leif
         Type:           |     Status:  new
  enhancement            |
     Priority:  major    |  Milestone:  1.12.0
    Component:  code-    |    Version:  1.1.0
  peerselection          |   Keywords:  availability preservation cache
   Resolution:           |  anti-censorship placement backend rollback add-
Launchpad Bug:           |  only
-------------------------+-------------------------------------------------

Comment (by dawuud):

 I've got this dev branch here:
 https://github.com/david415/tahoe-lafs/tree/introless-
 multiintro_yaml_config.0

 At first I made the web stuff output yaml but then I removed all the
 introducer-less web page config output because it's not very nice to make
 users copy/paste config options from a webpage. Instead I'm going to write
 a feature such that the yaml config is simply written to a file inside the
 tahoe config directory; HOWEVER we should have one yaml file per
 introducer. My question about this feature addition is: What should
 trigger the dumping of the intro'ed servers into the yaml files? Magic-
 Folder has a feature where the magic-folder client is not started until we
 have at least happiness storage servers available. We could do something
 like this or should we make a seperate HTTP api and CLI for this?

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