Commit ae97e5d5 authored by Ben Bodenmiller's avatar Ben Bodenmiller Committed by Achilleas Pipinellis

disable Rugged when switching to Gitaly without NFS

parent 1804c82d
...@@ -220,6 +220,9 @@ network, firewall, or name resolution problem preventing your GitLab ...@@ -220,6 +220,9 @@ network, firewall, or name resolution problem preventing your GitLab
server from reaching the Gitaly server then all Gitaly requests will server from reaching the Gitaly server then all Gitaly requests will
fail. fail.
Additionally, you need to
[disable Rugged if previously manually enabled](../high_availability/nfs.md#improving-nfs-performance-with-gitlab).
We assume that your Gitaly server can be reached at We assume that your Gitaly server can be reached at
`gitaly.internal:8075` from your GitLab server, and that Gitaly can read and `gitaly.internal:8075` from your GitLab server, and that Gitaly can read and
write to `/mnt/gitlab/default` and `/mnt/gitlab/storage1` respectively. write to `/mnt/gitlab/default` and `/mnt/gitlab/storage1` respectively.
......
...@@ -56,7 +56,8 @@ To do this, run the Rake task: ...@@ -56,7 +56,8 @@ To do this, run the Rake task:
sudo gitlab-rake gitlab:features:enable_rugged sudo gitlab-rake gitlab:features:enable_rugged
``` ```
If you need to undo this setting for some reason, run: If you need to undo this setting for some reason such as switching to [Gitaly without NFS](gitaly.md)
(recommended), run:
```sh ```sh
sudo gitlab-rake gitlab:features:disable_rugged sudo gitlab-rake gitlab:features:disable_rugged
......
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