diff options
| author | sytses <sytse@gitlab.com> | 2017-01-19 07:30:22 +0300 |
|---|---|---|
| committer | sytses <sytse@gitlab.com> | 2017-01-19 07:30:22 +0300 |
| commit | 51929b60403d0b99f4d5661404f4b329d333f04e (patch) | |
| tree | 6d0d3c74f85d9ce07f215001feb66a5341fd329e | |
| parent | d46f278aa9ae093014a0f38c19afd3a773a614d9 (diff) | |
DOcument router.
| -rw-r--r-- | README.md | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -87,6 +87,7 @@ All design decision should be added here. 1. Use gitaly-client or HTTP/websocket clients? gitlab-shell copies the SSH stream, both ways, to gitaly over a websocket, workhorse just forwards the request to Gitaly, let’s use HTTP. https://gitlab.com/gitlab-org/gitaly/issues/5#note_20294280 1. We will use [E3 from BitBucket to measure performance closely in isolation](https://gitlab.com/gitlab-org/gitaly/issues/34). 1. Use environment variables for setting configurations (see #20). +1. GitLab already has [logic so that the application servers know which file/git server contains what repository](https://docs.gitlab.com/ee/administration/repository_storages.html), this eliminates the need for a router. ## Iterate |