summaryrefslogtreecommitdiff
path: root/testing
diff options
context:
space:
mode:
authorDaniel Silverstone <dsilvers@digital-scurf.org>2017-01-02 15:48:36 +0000
committerDaniel Silverstone <dsilvers@digital-scurf.org>2017-01-02 15:48:36 +0000
commit8e0902f54fc9bb2c457e37d6dd11f89ffa3a9d9a (patch)
treecbf4177e1b1902a3d4797c0bafa5c98543f4c010 /testing
parentc3478c9421227977fa3672e31a4e7c901d9ae1fa (diff)
downloadgitano-8e0902f54fc9bb2c457e37d6dd11f89ffa3a9d9a.tar.gz
Some more notes in count-objects' yarn
Diffstat (limited to 'testing')
-rw-r--r--testing/02-commands-count-objects.yarn10
1 files changed, 10 insertions, 0 deletions
diff --git a/testing/02-commands-count-objects.yarn b/testing/02-commands-count-objects.yarn
index 8921358..abc84d3 100644
--- a/testing/02-commands-count-objects.yarn
+++ b/testing/02-commands-count-objects.yarn
@@ -1,5 +1,13 @@
<!-- -*- markdown -*- -->
+Counting objects
+================
+
+Git repositories are difficult to size without running `du` on the server-side.
+But there is an accepted standard way to find out how much is in a repository
+and that is to `git count-objects`. You need to be able to read a repository
+for Gitano to allow you to `count-objects` but otherwis it's fairly simple...
+
SCENARIO counting objects
GIVEN a standard instance
@@ -11,6 +19,8 @@ since that would be an information leak that the repository exists.
WHEN alice main, expecting failure, runs count-objects gitano-admin
THEN stderr contains CRIT: Ruleset denied action.
+But if we can read the repo, then we can tell what size it is.
+
WHEN testinstance adminkey runs count-objects gitano-admin
THEN stdout contains objects
AND stdout contains bytes