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
9109060c
Commit
9109060c
authored
Jun 22, 2017
by
Collen
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Move step 6 to be before step 4
parent
5514552c
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
19 additions
and
19 deletions
+19
-19
doc/gitlab-geo/configuration.md
doc/gitlab-geo/configuration.md
+19
-19
No files found.
doc/gitlab-geo/configuration.md
View file @
9109060c
...
...
@@ -129,7 +129,23 @@ sensitive data in the database. Any secondary node must have the
1. Save and close the file.
### Step 4. Enabling the secondary GitLab node
### Step 4. Regenerating the authorized keys in the secondary node
Regenerate the keys for `
~/.ssh/authorized_keys
`
(HTTPS clone will still work without this extra step).
On the **secondary** node where the database is [already replicated](./database.md),
run:
```
# For Omnibus installations
gitlab-rake gitlab:shell:setup
```
This will enable `
git
` operations to authorize against your existing users.
New users and SSH keys updated after this step, will be replicated automatically.
### Step 5. Enabling the secondary GitLab node
1. SSH into the **secondary** node and login as root:
...
...
@@ -165,9 +181,9 @@ The two most obvious issues that replication can have here are:
[Troubleshooting](#troubleshooting) section)
- Instance is firewalled (check your firewall rules)
### Step
5
. Replicating the repositories data
### Step
6
. Replicating the repositories data
G
etting a new secondary Geo node up and running, will also require the
Lastly, g
etting a new secondary Geo node up and running, will also require the
repositories data to be synced.
With GitLab **9.0** the syncing process starts automatically from the
...
...
@@ -222,22 +238,6 @@ While active repositories will be eventually replicated, if you don't rsync,
the files, any archived/inactive repositories will not get in the secondary node
as Geo doesn't run any routine task to look for missing repositories.
### Step 6. Regenerating the authorized keys in the secondary node
The final step is to regenerate the keys for `
~/.ssh/authorized_keys
`
(HTTPS clone will still work without this extra step).
On the **secondary** node where the database is [already replicated](./database.md),
run:
```
# For Omnibus installations
gitlab-rake gitlab:shell:setup
```
This will enable `
git
` operations to authorize against your existing users.
New users and SSH keys updated after this step, will be replicated automatically.
## Next steps
Your nodes should now be ready to use. You can login to the secondary node
...
...
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