gitlab-org--gitlab-foss/doc/administration/geo/replication/using_a_geo_server.md

---
stage: Enablement
group: Geo
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers
type: howto
---

<!-- Please update EE::GitLab::GeoGitAccess::GEO_SERVER_DOCS_URL if this file is moved) -->

# Using a Geo Server **(PREMIUM ONLY)**

After you set up the [database replication and configure the Geo nodes](index.md#setup-instructions), 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](https://about.gitlab.com/releases/2018/09/22/gitlab-11-3-released/) in [GitLab Premium](https://about.gitlab.com/pricing/#self-managed) 11.3.

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

```shell
$ git push
remote:
remote: You're pushing to a Geo secondary. We'll help you by proxying this
remote: request to the primary:
remote:
remote:   ssh://git@primary.geo/user/repo.git
remote:
Everything up-to-date
```
Add latest changes from gitlab-org/gitlab@master 2020-06-03 17:08:23 -04:00			`---`
			`stage: Enablement`
			`group: Geo`
			`info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers`
			`type: howto`
			`---`

Add latest changes from gitlab-org/gitlab@master 2020-04-21 14:09:31 -04:00			`<!-- Please update EE::GitLab::GeoGitAccess::GEO_SERVER_DOCS_URL if this file is moved) -->`
Docs: Merge EE doc/administration/geo to CE 2019-05-05 12:08:21 -04:00
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 04:50:38 -04:00			`# Using a Geo Server (PREMIUM ONLY)`
Docs: Merge EE doc/administration/geo to CE 2019-05-05 12:08:21 -04:00
Add latest changes from gitlab-org/gitlab@master 2020-04-01 02:07:50 -04:00			`After you set up the [database replication and configure the Geo nodes](index.md#setup-instructions), use your closest GitLab node as you would a normal standalone GitLab instance.`
Docs: Merge EE doc/administration/geo to CE 2019-05-05 12:08:21 -04:00
Add latest changes from gitlab-org/gitlab@master 2020-01-23 01:08:32 -05:00			`Pushing directly to a secondary node (for both HTTP, SSH including Git LFS) was [introduced](https://about.gitlab.com/releases/2018/09/22/gitlab-11-3-released/) in [GitLab Premium](https://about.gitlab.com/pricing/#self-managed) 11.3.`
Docs: Merge EE doc/administration/geo to CE 2019-05-05 12:08:21 -04:00
			`Example of the output you will see when pushing to a secondary node:`

Add latest changes from gitlab-org/gitlab@master 2020-01-30 10:09:15 -05:00			```shell
Docs: Merge EE doc/administration/geo to CE 2019-05-05 12:08:21 -04:00			`$ git push`
Add latest changes from gitlab-org/gitlab@master 2019-10-23 14:06:07 -04:00			`remote:`
			`remote: You're pushing to a Geo secondary. We'll help you by proxying this`
			`remote: request to the primary:`
			`remote:`
			`remote: ssh://git@primary.geo/user/repo.git`
			`remote:`
Docs: Merge EE doc/administration/geo to CE 2019-05-05 12:08:21 -04:00			`Everything up-to-date`
			```