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
0
Merge Requests
0
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
Boxiang Sun
gitlab-ce
Commits
049e4fe4
Commit
049e4fe4
authored
6 years ago
by
Ben Bodenmiller
Committed by
Achilleas Pipinellis
6 years ago
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
cleanup application server setup
parent
35a02dc3
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
12 additions
and
12 deletions
+12
-12
doc/administration/high_availability/gitlab.md
doc/administration/high_availability/gitlab.md
+12
-12
No files found.
doc/administration/high_availability/gitlab.md
View file @
049e4fe4
...
@@ -76,24 +76,23 @@ for each GitLab application server in your environment.
...
@@ -76,24 +76,23 @@ for each GitLab application server in your environment.
In a typical HA setup, this will be the url of the load balancer which will
In a typical HA setup, this will be the url of the load balancer which will
route traffic to all 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.
> **Note:** When you specify `https` in the `external_url`, as in the example
above, GitLab assumes you have SSL certificates in `/etc/gitlab/ssl/`. If
certificates are not present, Nginx will fail to start. See
[Nginx documentation](http://docs.gitlab.com/omnibus/settings/nginx.html#enable-https)
for more information.
## First 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
**only on**
the first GitLab application server.
It is not necessary to
run this on additional application servers.
Do not
run this on additional application servers.
1.
Initialize the database by running
`sudo gitlab-rake gitlab:setup`
.
1.
Initialize the database by running
`sudo gitlab-rake gitlab:setup`
.
1.
Run
`sudo gitlab-ctl reconfigure`
to compile the configuration.
> **WARNING:** Only run this setup task on **NEW** GitLab instances because it
> **WARNING:** Only run this setup task on **NEW** GitLab instances because it
will wipe any existing data.
will wipe any existing data.
> **Note:** When you specify `https` in the `external_url`, as in the example
above, GitLab assumes you have SSL certificates in
`/etc/gitlab/ssl/`
. If
certificates are not present, Nginx will fail to start. See
[
Nginx documentation
](
http://docs.gitlab.com/omnibus/settings/nginx.html#enable-https
)
for more information.
## Extra configuration for additional GitLab application servers
## Extra configuration for additional GitLab application servers
Additional GitLab servers (servers configured
**after**
the first GitLab server)
Additional GitLab servers (servers configured
**after**
the first GitLab server)
...
@@ -101,8 +100,7 @@ need some extra configuration.
...
@@ -101,8 +100,7 @@ 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
`/etc/gitlab/gitlab.rb`
**prior to**
running the first
`reconfigure`
in
`/etc/gitlab/gitlab.rb`
**prior to**
running the first
`reconfigure`
.
the steps above.
```ruby
```ruby
gitlab_shell['secret_token'] = 'fbfb19c355066a9afb030992231c4a363357f77345edd0f2e772359e5be59b02538e1fa6cae8f93f7d23355341cea2b93600dab6d6c3edcdced558fc6d739860'
gitlab_shell['secret_token'] = 'fbfb19c355066a9afb030992231c4a363357f77345edd0f2e772359e5be59b02538e1fa6cae8f93f7d23355341cea2b93600dab6d6c3edcdced558fc6d739860'
...
@@ -115,6 +113,8 @@ need some extra configuration.
...
@@ -115,6 +113,8 @@ need some extra configuration.
from running on upgrade. Only the primary GitLab application server should
from running on upgrade. Only the primary GitLab application server should
handle migrations.
handle migrations.
1.
Run
`sudo gitlab-ctl reconfigure`
to compile the configuration.
## Troubleshooting
## Troubleshooting
-
`mount: wrong fs type, bad option, bad superblock on`
-
`mount: wrong fs type, bad option, bad superblock on`
...
...
This diff is collapsed.
Click to expand it.
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