[tahoe-lafs-trac-stream] [tahoe-lafs] #1159: stop using .tac files: make it possible to change appname, Python package-directory name, perhaps other names

[tahoe-lafs]

#1159: stop using .tac files: make it possible to change appname, Python package-
directory name, perhaps other names
--------------------------------+-------------------------------------------
     Reporter:  davidsarah      |       Owner:  somebody                                                            
         Type:  defect          |      Status:  new                                                                 
     Priority:  major           |   Milestone:  eventually                                                          
    Component:  code-nodeadmin  |     Version:  1.8β                                                                
   Resolution:                  |    Keywords:  test-needed backward-compatibility forward-compatibility appname tac
Launchpad Bug:                  |  
--------------------------------+-------------------------------------------

Comment (by davidsarah):

 Replying to [comment:12 warner]:
 > Oh, one caveat: since we delegate daemonization/etc to {{{twistd}}},
 we're limited in the set of entry points we can use. The easiest one is
 {{{twisted.scripts.twistd.run}}}, for which the arguments are effectively
 {{{sys.argv}}}, which means it really wants to find a {{{.tac}}} file.
 What we want is a way to build the
 {{{twisted.application.service.Application}}} or {{{.MultiService}}}
 instance and hand it fully-formed into twistd. So we'd need to find a
 stable/reasonable point-of-entry into the twistd code that accepts a
 Service but is still before the daemonization/logging/etc setup.

 Or we can put a {{{.tac}}} file in the source tree, and direct twistd to
 that one (using something like
 {{{os.path.join(os.path.dirname(allmydata.__file__),
 'tahoe_node.tac')}}}), rather than to the one in the node directory. Even
 though it doesn't "stop using .tac files", that would solve the problems
 in this ticket because the in-source {{{.tac}}} can change without any
 compatibility issues.

 This depends on the Tahoe source not being zipped, but we already say in
 [source:setup.py] that it is not zip-safe.

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