[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2325: maybe stop using tac files to indicate node type?
Tahoe-LAFS
trac at tahoe-lafs.org
Sat Sep 10 06:56:27 UTC 2016
#2325: maybe stop using tac files to indicate node type?
--------------------------------+------------------------
Reporter: daira | Owner: warner
Type: defect | Status: new
Priority: normal | Milestone: eventually
Component: code-nodeadmin | Version: 1.10.0
Resolution: | Keywords: cli config
Launchpad Bug: |
--------------------------------+------------------------
Changes (by warner):
* milestone: undecided => eventually
Comment:
I'd like to get rid of these files, because when I want to edit
`tahoe.cfg`, I type "ta TAB", but my editor/shell won't fully complete for
me, because `tahoe-client.tac` shares a prefix. A minor reason, I'll admit
:).
The question is what signal should indicate the node type? I think the
main question is client/server vs introducer, and the presence of a
`[client]` section in `tahoe.cfg` is a good indicator (perhaps look for
either `[client]` or `[storage]`, to accomodate future server-only no-
client nodes, which would have `[storage]` but not `[client]`).
--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2325#comment:3>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage
More information about the tahoe-lafs-trac-stream
mailing list