[tahoe-lafs-trac-stream] [tahoe-lafs] #1487: remove the notion of "rootcap" from FTP-and-SFTP.rst

[tahoe-lafs]

#1487: remove the notion of "rootcap" from FTP-and-SFTP.rst
-----------------------------+--------------------------------
     Reporter:  zooko        |      Owner:  nobody
         Type:  enhancement  |     Status:  new
     Priority:  major        |  Milestone:  undecided
    Component:  unknown      |    Version:  1.8.2
   Resolution:               |   Keywords:  docs usability ftp
Launchpad Bug:               |
-----------------------------+--------------------------------

Comment (by davidsarah):

 The cap that is used as the root for an FTP/SFTP user account doesn't have
 any requirement or expectation that it not be stored in a Tahoe directory.
 (It is stored in the ftp.accounts file, but could easily be stored in a
 directory as well.) It's just any old directory cap, used in a particular
 way.

 As far as I understood, the reason why some of our docs use the term
 "rootcap" is a historical one: at one point we only supported a single
 root for each user's "vdrive". Now that a path can start with any URI or
 any of multiple aliases (in the CLI at least, and #1346 would also give an
 alternative to logging in with a username and password in FTP/SFTP),
 there's no need for that concept.

 OTOH, I think "root directory cap" in the original text meant "cap to an
 FTP or SFTP root directory". So I think it would be clearer to say:
 {{{
 ... and second to decide what directory cap should be used as the root
 directory
 for a log-in by the authenticated user.
 }}}

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