[tahoe-lafs-trac-stream] [Tahoe-LAFS] #1952: rename "tahoe backup" to "tahoe snapshot"

[Tahoe-LAFS]

#1952: rename "tahoe backup" to "tahoe snapshot"
---------------------------------+-----------------------------------------
     Reporter:  zooko            |      Owner:
         Type:  enhancement      |     Status:  new
     Priority:  normal           |  Milestone:  undecided
    Component:  code-frontend-   |    Version:  1.9.2
  cli                            |   Keywords:  tahoe-backup usability docs
   Resolution:                   |
Launchpad Bug:                   |
---------------------------------+-----------------------------------------

Comment (by daira):

 Replying to [comment:8 ambimorph]:
 > I just went through a similar experience as described in
 [https://github.com/LeastAuthority/leastauthority.com/issues/196 Taylor's
 S4 Usability Notes] for the tahoe-LAFS part in terms of managing the
 interfaces (both web and command line), and trying to not so much
 *restore* but even *find* the files that I backed up.  I independently
 discovered this same discussion about backup vs. snapshot, and `tahoe cp
 -r`.
 >
 > I now don't understand why I would ever use `backup` instead of `cp -r`,
 if I want to be able to navigate the files later.  It also took me a long
 time to figure out how to get the top level directory included in the
 `cp`, by repeating the name of it after the alias.

 `tahoe backup` backs up the whole directory structure; the use of the
 backupdb to not upload some files/directories is just an optimisation, and
 the corresponding links to already-uploaded objects are still made on the
 Tahoe side. Note that this depends on the structure created by `tahoe
 backup` being immutable. `tahoe cp -r` is not able to use this
 optimisation because it always creates mutable directories (the
 `--immutable` and `--use-backupdb` options mentioned in comment:7 are
 imagined future features).

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