[tahoe-lafs-trac-stream] [tahoe-lafs] #937: 'tahoe run' doesn't work for an introducer node

[tahoe-lafs]

#937: 'tahoe run' doesn't work for an introducer node
-------------------------+-------------------------------------------------
     Reporter:  Bryan    |      Owner:  davidsarah
  Larsen                 |     Status:  assigned
         Type:  defect   |  Milestone:  1.11.0
     Priority:  major    |    Version:  1.6.0
    Component:  code-    |   Keywords:  docs introducer tahoe-run review-
  frontend-cli           |  needed
   Resolution:           |
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by davidsarah):

 Replying to [comment:12 warner]:
 > ... (note that we didn't previously have coverage of 'tahoe run'
 either).

 That's #1121.

 > We might consider changing 'tahoe run' to use the "{{{twistd
 --nodaemon}}}"
 > approach, which would make it look a lot closer to {{{tahoe start}}}.
 > However, that would make it more dependent upon .tac files, not less. In
 > the longer run, I think we should try the approach I came up with in my
 >
 [https://github.com/warner/toolbed/blob/master/toolbed/scripts/startstop.py
 "toolbed" project],
 > where I create a (in-memory) twistd plugin that creates the desired
 > Node, then set up the twistd arguments that will invoke this plugin,
 > then give control to {{{twistd.runApp}}} in a child process.

 ... or use the approach I suggested in ticket:1159#comment:17 of using a
 {{{.tac}}} in the source tree. That solves the main version-skew problems
 with {{{.tac}}} files, and is possibly less disruptive to the existing
 code.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/937#comment:16>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage