[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2324: copy of introducer furl, aliases to new computer, error with alias but not alias's value

[Tahoe-LAFS]

#2324: copy of introducer furl, aliases to new computer, error with alias but not
alias's value
-----------------------------------+--------------------------------------
     Reporter:  jgillisp           |      Owner:  jgillisp
         Type:  defect             |     Status:  new
     Priority:  normal             |  Milestone:  undecided
    Component:  code-frontend-cli  |    Version:  1.10.0
   Resolution:                     |   Keywords:  usability new-user error
Launchpad Bug:                     |
-----------------------------------+--------------------------------------
Changes (by daira):

 * keywords:   => usability new-user error
 * owner:   => jgillisp
 * component:  unknown => code-frontend-cli


Comment:

 Aliases are read from the node directory in effect for the CLI command,
 which can be different from the base directory of the gateway. By default,
 this will be `~/.tahoe`, which explains the behaviour you saw. Remember
 that the CLI does not *in general* have the same filesystem hierarchy as
 the gateway, so it wouldn't be correct for it to take the gateway's base
 directory as its default node directory.

 To fix this, use `tahoe --node-directory=c:\asr\.tahoe check tahoe:` (this
 syntax assumes Tahoe-LAFS v1.10.0 or later). Alternatively you can make
 `~/.tahoe/private` contain the intended default `aliases` file.

 Is there any way we could have made this clearer in the docs?

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