aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLibravatar Rutger Broekhoff2024-04-26 23:26:28 +0200
committerLibravatar Rutger Broekhoff2024-04-26 23:26:28 +0200
commit14cf035c4f3a749ff696e2cf5bf08d11279a6918 (patch)
treea185942f381938c2c2104bc99c66e51c067fe0e8
parenta5c556ba0c922e00997ccb86bad93ea16768446d (diff)
downloadgitolfs3-14cf035c4f3a749ff696e2cf5bf08d11279a6918.tar.gz
gitolfs3-14cf035c4f3a749ff696e2cf5bf08d11279a6918.zip
Update README (I lied about Gitolfs3 not requiring any kind of storage)
-rw-r--r--README.md10
1 files changed, 6 insertions, 4 deletions
diff --git a/README.md b/README.md
index f639dfd..434e4da 100644
--- a/README.md
+++ b/README.md
@@ -23,10 +23,12 @@ Currently, it has the following features:
23 believe this was nice when wanting to push to some ssh://git@asdf/blabla.git 23 believe this was nice when wanting to push to some ssh://git@asdf/blabla.git
24 repo without having to type `/srv/git` before the repo name. And I don't want 24 repo without having to type `/srv/git` before the repo name. And I don't want
25 to have to use something like Gitolite.) 25 to have to use something like Gitolite.)
26- Gitolfs3 (the server, `git-lfs-authenticate` and `git-shell` implementation) 26- Gitolfs3 does not require any kind of persistent nor temporary storage for
27 do not require any kind of persistent nor temporary storage. Instead, user 27 token storage. Instead, user authentication/authorization between
28 authentication/authorization between `git-lfs-authenticate` and the Gitolfs3 28 `git-lfs-authenticate` and the Gitolfs3 server is done using HMAC(-SHA256)
29 server is done using HMAC(-SHA256) MACs. 29 MACs.
30- Limiting unauthenticated public downloads on a per-hour basis. Storage is
31 required for this. (This feature is implemented pretty badly.)
30- Public/private repos based on the `git-daemon-export-ok` file in the bare 32- Public/private repos based on the `git-daemon-export-ok` file in the bare
31 repo. (I have a very particular setup in which this is desirable.) 33 repo. (I have a very particular setup in which this is desirable.)
32 - Downloads for files in public repositories are 'proxied' through the 34 - Downloads for files in public repositories are 'proxied' through the