diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2019-10-02 15:06:04 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2019-10-02 15:06:04 +0300 |
| commit | 81c6c53d6cd5ffde1c070d987dc2985f662cb301 (patch) | |
| tree | 97ddbeb02373e8134edaa3e045f74d41d66cd500 /doc/migrate_ci_to_ce | |
| parent | f7e0be9bbe1173b0de18a52a21b49d19349f40b7 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/migrate_ci_to_ce')
| -rw-r--r-- | doc/migrate_ci_to_ce/README.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/migrate_ci_to_ce/README.md b/doc/migrate_ci_to_ce/README.md index 4a96001f2de..85e69be6516 100644 --- a/doc/migrate_ci_to_ce/README.md +++ b/doc/migrate_ci_to_ce/README.md @@ -268,11 +268,11 @@ If you installed GitLab CI from source we now need to configure a redirect in NGINX so that existing CI runners can keep using the old CI server address, and so that existing links to your CI server keep working. -### 1. Update Nginx configuration +### 1. Update NGINX configuration To ensure that your existing CI runners are able to communicate with the migrated installation, and that existing build triggers still work, you'll need -to update your Nginx configuration to redirect requests for the old locations to +to update your NGINX configuration to redirect requests for the old locations to the new ones. Edit `/etc/nginx/sites-available/gitlab_ci` and paste: @@ -324,13 +324,13 @@ You should also make sure that you can: 1. `curl https://YOUR_GITLAB_SERVER_FQDN/` from your previous GitLab CI server. 1. `curl https://YOUR_CI_SERVER_FQDN/` from your GitLab CE (or EE) server. -### 2. Check Nginx configuration +### 2. Check NGINX configuration ```sh sudo nginx -t ``` -### 3. Restart Nginx +### 3. Restart NGINX ```sh sudo /etc/init.d/nginx restart |