debian-mirror-gitlab/doc/administration/geo/replication/using_a_geo_server.md

28 lines
1.1 KiB
Markdown
Raw Normal View History

2020-06-23 00:09:42 +05:30
---
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
---
2020-05-24 23:13:21 +05:30
<!-- Please update EE::GitLab::GeoGitAccess::GEO_SERVER_DOCS_URL if this file is moved) -->
2019-07-31 22:56:46 +05:30
2019-09-30 21:07:59 +05:30
# Using a Geo Server **(PREMIUM ONLY)**
2019-07-31 22:56:46 +05:30
2020-11-24 15:15:51 +05:30
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.
2019-07-31 22:56:46 +05:30
2020-03-13 15:44:24 +05:30
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.
2019-07-31 22:56:46 +05:30
Example of the output you will see when pushing to a **secondary** node:
2020-03-13 15:44:24 +05:30
```shell
2019-07-31 22:56:46 +05:30
$ git push
2019-12-26 22:10:19 +05:30
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:
2019-07-31 22:56:46 +05:30
Everything up-to-date
```