diff options
| author | Daniel Silverstone <dsilvers@digital-scurf.org> | 2017-01-02 15:58:26 +0000 |
|---|---|---|
| committer | Daniel Silverstone <dsilvers@digital-scurf.org> | 2017-01-02 15:58:26 +0000 |
| commit | 22dfcb27fa1e47d333238ed0ffad17a268b09351 (patch) | |
| tree | db143e669898ab889201be90a750f00eb7d093a5 /testing | |
| parent | 1984d79d3f55255308cafe1fd8b30b339847ad5e (diff) | |
| download | gitano-22dfcb27fa1e47d333238ed0ffad17a268b09351.tar.gz | |
More explanation in the graveyard yarn
Diffstat (limited to 'testing')
| -rw-r--r-- | testing/02-commands-graveyard.yarn | 24 |
1 files changed, 23 insertions, 1 deletions
diff --git a/testing/02-commands-graveyard.yarn b/testing/02-commands-graveyard.yarn index 98e8220..1decc4d 100644 --- a/testing/02-commands-graveyard.yarn +++ b/testing/02-commands-graveyard.yarn @@ -1,5 +1,19 @@ <!-- -*- markdown -*- --> +Looking after the dead +====================== + +Earlier we talked about how `destroy` allows the owner of a repository (or +someone with delegated access) to remove a repository from a Gitano server. At +the time we said this was a two-part process and `graveyard` is the other half +of the story. + +When repositories are destroyed they are not removed from the filesystem. +Instead they go to live in a special directory called the graveyard, which is +separate from the repository root. Only the `graveyard` command can interact +with these destroyed repositories. + + _.---,._,' /' _.--.< /' `' @@ -16,6 +30,11 @@ \ \\| 2008-2016 |// ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +When a user owns a repository, they are permitted to destroy it, they will no +longer be able to see if in the output of the `ls` command and unless the +administrator of the Gitano instance has done some ACL trickery, they will not +be able to then look into the graveyard to see it. + SCENARIO graveyard GIVEN a standard instance @@ -29,10 +48,13 @@ THEN stdout does not contain personal/alice/testrepo When a repository is deleted it is put in the graveyard. -By default only admin users may browse the graveyard and restore repositories. +By default normal users are not allowed to look at the graveyard... WHEN alice main, expecting failure, runs graveyard list THEN stderr contains CRIT: You may not perform site administration + +...and only admin users may browse the graveyard and restore repositories. + WHEN testinstance adminkey runs graveyard list THEN stdout contains personal.alice.testrepo.*\.destroyed |