Commit 48c1968c authored by ernstvn's avatar ernstvn

Rename the after setup page and update links to it

parent f364b2c1
...@@ -144,7 +144,7 @@ If you installed GitLab using the Omnibus packages (highly recommended): ...@@ -144,7 +144,7 @@ If you installed GitLab using the Omnibus packages (highly recommended):
1. [Configure SSH authorizations to use the database](ssh.md) 1. [Configure SSH authorizations to use the database](ssh.md)
1. [Configure GitLab](configuration.md) to set the primary and secondary nodes. 1. [Configure GitLab](configuration.md) to set the primary and secondary nodes.
1. Optional: [Configure a secondary LDAP server](../administration/auth/ldap.md) for the secondary. See [notes on LDAP](#ldap). 1. Optional: [Configure a secondary LDAP server](../administration/auth/ldap.md) for the secondary. See [notes on LDAP](#ldap).
1. [Follow the after setup steps](after_setup.md). 1. [Follow the "Using a Geo Server" guide](using_a_geo_server.md).
[install-ee]: https://about.gitlab.com/downloads-ee/ "GitLab Enterprise Edition Omnibus packages downloads page" [install-ee]: https://about.gitlab.com/downloads-ee/ "GitLab Enterprise Edition Omnibus packages downloads page"
...@@ -160,7 +160,7 @@ If you installed GitLab from source: ...@@ -160,7 +160,7 @@ If you installed GitLab from source:
1. [Configure SSH authorizations to use the database](ssh.md) 1. [Configure SSH authorizations to use the database](ssh.md)
1. [Configure GitLab](configuration_source.md) to set the primary and secondary 1. [Configure GitLab](configuration_source.md) to set the primary and secondary
nodes. nodes.
1. [Follow the after setup steps](after_setup.md). 1. [Follow the "Using a Geo Server" guide](using_a_geo_server.md).
[install-ee-source]: https://docs.gitlab.com/ee/install/installation.html "GitLab Enterprise Edition installation from source" [install-ee-source]: https://docs.gitlab.com/ee/install/installation.html "GitLab Enterprise Edition installation from source"
......
...@@ -157,7 +157,7 @@ correctly identified as a secondary Geo node and if Geo is enabled. ...@@ -157,7 +157,7 @@ correctly identified as a secondary Geo node and if Geo is enabled.
If your installation isn't working properly, check the If your installation isn't working properly, check the
[troubleshooting](#troubleshooting) section. [troubleshooting](#troubleshooting) section.
Point your users to the [after setup steps](after_setup.md). Point your users to the ["Using a Geo Server" guide](using_a_geo_server.md).
## Selective replication ## Selective replication
......
...@@ -176,7 +176,7 @@ correctly identified as a secondary Geo node and if Geo is enabled. ...@@ -176,7 +176,7 @@ correctly identified as a secondary Geo node and if Geo is enabled.
If your installation isn't working properly, check the If your installation isn't working properly, check the
[troubleshooting](configuration.md#troubleshooting) section. [troubleshooting](configuration.md#troubleshooting) section.
Point your users to the [after setup steps](after_setup.md). Point your users to the ["Using a Geo Server" guide](using_a_geo_server.md).
## Selective replication ## Selective replication
......
# After setup # Using a Geo Server
After you set up the [database replication and configure the GitLab Geo nodes][req], After you set up the [database replication and configure the GitLab Geo nodes][req],
there are a few things to consider: there are a few things to consider:
...@@ -6,13 +6,13 @@ there are a few things to consider: ...@@ -6,13 +6,13 @@ there are a few things to consider:
1. Users need an extra step to be able to fetch code from the secondary and push 1. Users need an extra step to be able to fetch code from the secondary and push
to primary: to primary:
1. Clone the repository as normal do from the secondary node: 1. Clone the repository as you would normally do, but from the secondary node:
```bash ```bash
git clone git@secondary.gitlab.example.com:user/repo.git git clone git@secondary.gitlab.example.com:user/repo.git
``` ```
1. Change the remote push URL following this example: 1. Change the remote push URL to always push to primary, following this example:
```bash ```bash
git remote set-url --push origin git@primary.gitlab.example.com:user/repo.git git remote set-url --push origin git@primary.gitlab.example.com:user/repo.git
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment