diff options
| author | Amy Qualls <aqualls@gitlab.com> | 2022-02-15 07:49:11 -0800 |
|---|---|---|
| committer | Amy Qualls <aqualls@gitlab.com> | 2022-02-15 07:49:11 -0800 |
| commit | 91ea741ff3e4171df11f6e205083a80c837469a9 (patch) | |
| tree | 6bb89f7f691db6ce8be37f25142c1924e247e013 | |
| parent | 0e0b6ccd990257286497837e201ea7e70f9c023e (diff) | |
| download | gitlab-shell-91ea741ff3e4171df11f6e205083a80c837469a9.tar.gz | |
Fix link in README
Shouldn't start with a leading slash.
| -rw-r--r-- | README.md | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -18,7 +18,7 @@ An overview of the four cases described above: 1. git pull over SSH -> gitlab-shell -> API call to gitlab-rails (Authorization) -> accept or decline -> establish Gitaly session 1. git push over SSH -> gitlab-shell (git command is not executed yet) -> establish Gitaly session -> (in Gitaly) gitlab-shell pre-receive hook -> API call to gitlab-rails (authorization) -> accept or decline push -[Full feature list](/doc/features.md) +[Full feature list](doc/features.md) ## Code status @@ -115,7 +115,7 @@ guidelines: GitLab Shell performs rate-limiting by user account and project for git operations. GitLab Shell accepts git operation requests and then makes a call to the Rails rate-limiter (backed by Redis). If the `user + project` exceeds the rate limit then GitLab Shell will then drop further connection requests for that `user + project`. -The rate-limiter is applied at the git command (plumbing) level. Each command has a rate limit of 600/minute. For example, `git push` has 600/minute and `git pull` has another 600/minute. +The rate-limiter is applied at the git command (plumbing) level. Each command has a rate limit of 600/minute. For example, `git push` has 600/minute and `git pull` has another 600/minute. Because they are using the same plumbing command `git-upload-pack`, `git pull` and `git clone` are in effect the same command for the purposes of rate-limiting. |