[tahoe-lafs-trac-stream] [Tahoe-LAFS] #1310: separate "gateway state directory" from "client state directory"

[Tahoe-LAFS]

#1310: separate "gateway state directory" from "client state directory"
-----------------------------------+-----------------------
     Reporter:  zooko              |      Owner:  warner
         Type:  defect             |     Status:  reopened
     Priority:  major              |  Milestone:  undecided
    Component:  code-frontend-cli  |    Version:  1.8.1
   Resolution:                     |   Keywords:  usability
Launchpad Bug:                     |
-----------------------------------+-----------------------

Comment (by zooko):

 Replying to [comment:14 warner]:
 >
 > Rereading zooko's initial issue, I found myself tempted to yell out
 "don't do that!". I guess I've always optimized tahoe's frontend- and
 setup- management tools for the common case of a single "gateway" per
 (user*computer) tuple. I really want the instructions to be as simple as
 "tahoe create; tahoe start; tahoe webopen". I don't want to complicate
 that for the sake of the less-common use case of multiple
 nodes/gateways/clients/whatevers.
 …
 > Anyways, that was a long diversion away from the main point: the use of
 a single NODEDIR to manage the states and configurations of all these
 pieces (client-ish stuff, agent-ish stuff, gateway-ish stuff, heck even
 server-ish stuff) is ideal for one-grid cases, and confusing for multiple-
 grid cases.

 I'm not sure if the "separate dirs for separate state" approach ''is'' any
 more complicated, at least for the end user.

 Specifically, for the proposal Brian suggests here:

 > I'm warming slightly to the `--cli-directory=` idea. Maybe by splitting
 these different bits of functionality into separate subdirs, putting all
 of them in the single NODEDIR by default, but making it clear that e.g.
 CLI commands only touch stuff in NODEDIR/cli/* . Then make it possible to
 either override the top-level `--nodedir=`, or a CLI-functionality-
 specific `--cli-directory=`.

 What impact would this have on the end-user-visible CLI flow, such as the
 {{{tahoe create; tahoe start; tahoe webopen}}} that Brian mentioned?

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