BigW Consortium Gitlab

Commit 9a40b3cc by Jacob Vosmaer (GitLab) Committed by Rémy Coutable

Clarify when disabling Gitaly makes sense

parent 2aa2731c
...@@ -2,7 +2,9 @@ ...@@ -2,7 +2,9 @@
[Gitaly](https://gitlab.com/gitlab-org/gitaly) (introduced in GitLab [Gitaly](https://gitlab.com/gitlab-org/gitaly) (introduced in GitLab
9.0) is a service that provides high-level RPC access to Git 9.0) is a service that provides high-level RPC access to Git
repositories. Gitaly is a mandatory component in GitLab 9.4 and newer. repositories. Gitaly was optional when it was first introduced in
GitLab, but since GitLab 9.4 it is a mandatory component of the
application.
GitLab components that access Git repositories (gitlab-rails, GitLab components that access Git repositories (gitlab-rails,
gitlab-shell, gitlab-workhorse) act as clients to Gitaly. End users do gitlab-shell, gitlab-workhorse) act as clients to Gitaly. End users do
...@@ -184,14 +186,20 @@ Gitaly logs on your Gitaly server (`sudo gitlab-ctl tail gitaly` or ...@@ -184,14 +186,20 @@ Gitaly logs on your Gitaly server (`sudo gitlab-ctl tail gitaly` or
coming in. One sure way to trigger a Gitaly request is to clone a coming in. One sure way to trigger a Gitaly request is to clone a
repository from your GitLab server over HTTP. repository from your GitLab server over HTTP.
## Disabling or enabling the Gitaly service ## Disabling or enabling the Gitaly service in a cluster environment
If you are running Gitaly [as a remote If you are running Gitaly [as a remote
service](#running-gitaly-on-its-own-server) you may want to disable service](#running-gitaly-on-its-own-server) you may want to disable
the local Gitaly service that runs on your Gitlab server by default. the local Gitaly service that runs on your Gitlab server by default.
To disable the Gitaly service in your Omnibus installation, add the > 'Disabling Gitaly' only makes sense when you run GitLab in a custom
following line to `/etc/gitlab/gitlab.rb`: cluster configuration, where different services run on different
machines. Disabling Gitaly on all machines in the cluster is not a
valid configuration.
If you are setting up a GitLab cluster where Gitaly does not need to
run on all machines, you can disable the Gitaly service in your
Omnibus installation, add the following line to `/etc/gitlab/gitlab.rb`:
```ruby ```ruby
gitaly['enable'] = false gitaly['enable'] = false
...@@ -200,11 +208,13 @@ gitaly['enable'] = false ...@@ -200,11 +208,13 @@ gitaly['enable'] = false
When you run `gitlab-ctl reconfigure` the Gitaly service will be When you run `gitlab-ctl reconfigure` the Gitaly service will be
disabled. disabled.
To disable the Gitaly service in an installation from source, add the To disable the Gitaly service in a GitLab cluster where you installed
following to `/etc/default/gitlab`: GitLab from source, add the following to `/etc/default/gitlab` on the
machine where you want to disable Gitaly.
```shell ```shell
gitaly_enabled=false gitaly_enabled=false
``` ```
When you run `service gitlab restart` Gitaly will be disabled. When you run `service gitlab restart` Gitaly will be disabled on this
particular machine.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment