diff options
author | John Cai <jcai@gitlab.com> | 2019-07-02 20:29:13 +0300 |
---|---|---|
committer | John Cai <jcai@gitlab.com> | 2019-07-02 20:29:13 +0300 |
commit | cb59c3fa0b08bfb6ecf0e896d89ac6dd23b3a09b (patch) | |
tree | 581ba3e959d9e92a2bcb9f6b7275866d1c891d8d | |
parent | d6f1029199554f47d70ee1b616a334d22a63af98 (diff) | |
parent | 216db858785ebf708d8d3e8e4852cb3441781a13 (diff) |
Merge branch 'zj-docs-gitaly-ruby' into 'master'
Remove vendoring documentation for Gitlab::Git
See merge request gitlab-org/gitaly!1343
-rw-r--r-- | ruby/README.md | 14 |
1 files changed, 2 insertions, 12 deletions
diff --git a/ruby/README.md b/ruby/README.md index ce947a6b7..1ff0f473a 100644 --- a/ruby/README.md +++ b/ruby/README.md @@ -2,8 +2,8 @@ `gitaly-ruby` is a 'sidecar' process for the main Gitaly service. It allows us to run legacy Ruby application code for which it would be -too risky or even infeasible to port it to Go. It will also speed up -the Gitaly migration project. +too risky or even infeasible to port it to Go. It was introduced to +speed up the Gitaly migration project. ## Architecture @@ -35,16 +35,6 @@ tests only, without recompiling the Go parts then do the following: - edit code under the current directory (`ruby`); - run `bundle exec rspec` in the current directory. -## Vendored copy of Gitlab::Git - -`gitaly-ruby` contains a vendored copy of `lib/gitlab/git` from -https://gitlab.com/gitlab-org/gitlab-ce. This allows us to share code -between gitlab-ce / gitlab-ee and `gitaly-ruby`. - -To update the vendored copy of Gitlab::Git, run -`_support/vendor-gitlab-git COMMIT_ID` from the root of the Gitaly -repository. - ## Development Gitaly-ruby is only meant to be spawned by Gitaly itself. But, during |