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
db8d5fc2
Commit
db8d5fc2
authored
Jul 27, 2017
by
Chenjerai Katanda
Committed by
Drew Blessing
Jul 27, 2017
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update server terminolgy to differentiate HA setups from Geo
parent
467979c6
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
9 additions
and
9 deletions
+9
-9
doc/administration/high_availability/gitlab.md
doc/administration/high_availability/gitlab.md
+9
-9
No files found.
doc/administration/high_availability/gitlab.md
View file @
db8d5fc2
...
@@ -5,7 +5,7 @@ configure the GitLab application server(s) now. Complete the steps below
...
@@ -5,7 +5,7 @@ configure the GitLab application server(s) now. Complete the steps below
for each GitLab application server in your environment.
for each GitLab application server in your environment.
> **Note:** There is some additional configuration near the bottom for
> **Note:** There is some additional configuration near the bottom for
secondary
GitLab application servers. It's important to read and understand
additional
GitLab application servers. It's important to read and understand
these additional steps before proceeding with GitLab installation.
these additional steps before proceeding with GitLab installation.
1.
If necessary, install the NFS client utility packages using the following
1.
If necessary, install the NFS client utility packages using the following
...
@@ -72,14 +72,14 @@ for each GitLab application server in your environment.
...
@@ -72,14 +72,14 @@ for each GitLab application server in your environment.
```
```
> **Note:** To maintain uniformity of links across HA clusters, the `external_url`
> **Note:** To maintain uniformity of links across HA clusters, the `external_url`
on the
master as well as all secondary application servers should point to the
on the
first application server as well as the additional application
eventual url that users will use to access GitLab. In a typical HA setup,
servers should point to the external url that users will use to access GitLab.
this will be the url of the load balancer which will route traffic to all
In a typical HA setup, this will be the url of the load balancer which will
GitLab application servers in the HA cluster.
route traffic to all
GitLab application servers in the HA cluster.
1.
Run
`sudo gitlab-ctl reconfigure`
to compile the configuration.
1.
Run
`sudo gitlab-ctl reconfigure`
to compile the configuration.
##
Primary
GitLab application server
##
First
GitLab application server
As a final step, run the setup rake task on the first GitLab application server.
As a final step, run the setup rake task on the first GitLab application server.
It is not necessary to run this on additional application servers.
It is not necessary to run this on additional application servers.
...
@@ -95,10 +95,10 @@ It is not necessary to run this on additional application servers.
...
@@ -95,10 +95,10 @@ It is not necessary to run this on additional application servers.
[
Nginx documentation
](
http://docs.gitlab.com/omnibus/settings/nginx.html#enable-https
)
[
Nginx documentation
](
http://docs.gitlab.com/omnibus/settings/nginx.html#enable-https
)
for more information.
for more information.
##
Additional configuration for secondary
GitLab application servers
##
Extra configuration for additional
GitLab application servers
Secondary
GitLab servers (servers configured
**after**
the first GitLab server)
Additional
GitLab servers (servers configured
**after**
the first GitLab server)
need some
additional
configuration.
need some
extra
configuration.
1.
Configure shared secrets. These values can be obtained from the primary
1.
Configure shared secrets. These values can be obtained from the primary
GitLab server in
`/etc/gitlab/gitlab-secrets.json`
. Add these to
GitLab server in
`/etc/gitlab/gitlab-secrets.json`
. Add these to
...
...
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