gitlab-org--gitlab-foss/doc/administration/geo/replication/using_a_geo_server.md
Marcel Amirault 73c6477b7e Changing badges to use parentheses not brackets
Previously, we used brackets to denote the tier badges,
but this made Kramdown, the docs site Markdown renderer,
show many warnings when building the site. This is now
fixed by using parentheses instead of square brackets.

This was caused by [PREMIUM] looking like a link to
Kramdown, which couldn't find a URL there.

See:
- https://gitlab.com/gitlab-com/gitlab-docs/merge_requests/484
- https://gitlab.com/gitlab-org/gitlab-ce/issues/63800
2019-07-08 08:50:38 +00:00

825 B

Using a Geo Server (PREMIUM ONLY)

After you set up the database replication and configure the Geo nodes, use your closest GitLab node as you would a normal standalone GitLab instance.

Pushing directly to a secondary node (for both HTTP, SSH including git-lfs) was introduced in GitLab Premium 11.3.

Example of the output you will see when pushing to a secondary node:

$ git push
> GitLab: You're pushing to a Geo secondary.
> GitLab: We'll help you by proxying this request to the primary: ssh://git@primary.geo/user/repo.git
Everything up-to-date