Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
d9a03cf2
Commit
d9a03cf2
authored
Feb 27, 2021
by
Ben Bodenmiller
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Gitaly cleanup
parent
93bdc328
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
10 additions
and
6 deletions
+10
-6
doc/administration/gitaly/index.md
doc/administration/gitaly/index.md
+10
-6
No files found.
doc/administration/gitaly/index.md
View file @
d9a03cf2
...
...
@@ -235,6 +235,7 @@ Method 2:
### Configure Gitaly servers
On the Gitaly servers, you must configure storage paths and enable the network listener.
The Gitaly server must be able to read, write, and set permissions on the configured path.
If you want to reduce the risk of downtime when you enable authentication, you can temporarily
disable enforcement. For more information, see the documentation on configuring
...
...
@@ -250,8 +251,6 @@ disable enforcement. For more information, see the documentation on configuring
-->
```
ruby
# /etc/gitlab/gitlab.rb
# Avoid running unnecessary services on the Gitaly server
postgresql
[
'enable'
]
=
false
redis
[
'enable'
]
=
false
...
...
@@ -285,6 +284,10 @@ disable enforcement. For more information, see the documentation on configuring
# Don't forget to copy `/etc/gitlab/gitlab-secrets.json` from Gitaly client to Gitaly server.
gitlab_rails
[
'internal_api_url'
]
=
'https://gitlab.example.com'
# Authentication token to ensure only authorized servers can communicate with
# Gitaly server
gitaly
[
'auth_token'
]
=
'AUTH_TOKEN'
# Make Gitaly accept connections on all network interfaces. You must use
# firewalls to restrict access to this address/port.
# Comment out following line if you only want to support TLS connections
...
...
@@ -387,10 +390,10 @@ if previously enabled manually.
Gitaly makes the following assumptions:
-
Your
`gitaly1.internal`
Gitaly server can be reached at
`gitaly1.internal:8075`
from your Gitaly
clients, and that Gitaly server can read, write, and set permissions on
`/
mnt/gitlab/default
`
and
`/mnt/gitlab/
storage1
`
.
clients, and that Gitaly server can read, write, and set permissions on
`/
var/opt/gitlab/git-data
`
and
`/mnt/gitlab/
git-data
`
.
-
Your
`gitaly2.internal`
Gitaly server can be reached at
`gitaly2.internal:8075`
from your Gitaly
clients, and that Gitaly server can read, write, and set permissions on
`/
mnt/gitlab/storage2
`
.
clients, and that Gitaly server can read, write, and set permissions on
`/
srv/gitlab/git-data
`
.
-
Your
`gitaly1.internal`
and
`gitaly2.internal`
Gitaly servers can reach each other.
You can't define Gitaly servers with some as a local Gitaly server
...
...
@@ -595,7 +598,8 @@ To configure Gitaly with TLS:
```
1.
Copy all Gitaly server certificates (or their certificate authority) to
`/etc/gitlab/trusted-certs`
so that Gitaly servers trust the certificate when calling into themselves
`/etc/gitlab/trusted-certs`
on all Gitaly servers and clients
so that Gitaly servers and clients trust the certificate when calling into themselves
or other Gitaly servers:
```
shell
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment