Update links to docs (from /ce to /ee)

README.md

@@ -104,7 +104,7 @@ See [doc/settings/smtp.md](doc/settings/smtp.md).
 #### Omniauth (Google, Twitter, GitHub login)
 Omniauth configuration is documented in
-[docs.gitlab.com](https://docs.gitlab.com/ce/integration/omniauth.html).
+[docs.gitlab.com](https://docs.gitlab.com/ee/integration/omniauth.html).
 #### Adjusting Unicorn settings
@@ -223,7 +223,7 @@ See [doc/settings/backups.md](doc/settings/backups.md#creating-an-application-ba
 ### Restoring an application backup
-See [backup restore documentation](https://docs.gitlab.com/ce/raketasks/backup_restore.html#omnibus-installations).
+See [backup restore documentation](https://docs.gitlab.com/ee/raketasks/backup_restore.html#omnibus-installations).
 ### Backup and restore using non-packaged database

doc/README.md

@@ -20,7 +20,7 @@ Omnibus GitLab is a way to package different services and tools required to run
 ### Prerequisites
-- [Installation Requirements](https://docs.gitlab.com/ce/install/requirements.html)
+- [Installation Requirements](https://docs.gitlab.com/ee/install/requirements.html)
 - If you want to access your GitLab instance via a domain name, like mygitlabinstance.com, make sure the domain correctly points to the IP of the server where GitLab is being installed. You can check this using the command `host mygitlabinstance.com`
 - If you want to use HTTPS on your GitLab instance, make sure you have the SSL certificates for the domain ready. (Note that certain components like Container Registry which can have their own subdomains requires certificates for those subdomains also)
 - If you want to send notification emails, install and configure a mail server (MTA) like sendmail. Alternatively, you can use other third party SMTP servers, which is described below.
@@ -36,15 +36,15 @@ This section describes the commonly used configuration settings. Check
 - [Setting up a domain name/URL](https://docs.gitlab.com/omnibus/settings/configuration.html#configuring-the-external-url-for-gitlab) for the GitLab Instance so that it can be accessed easily
 - [Enabling HTTPS](https://docs.gitlab.com/omnibus/settings/nginx.html#enable-https)
 - [Enabling notification emails](https://docs.gitlab.com/omnibus/settings/smtp.html#smtp-settings)
-- [Enabling replying via email](https://docs.gitlab.com/ce/administration/reply_by_email.html#set-it-up)
-  - [Installing and configuring postfix](https://docs.gitlab.com/ce/administration/reply_by_email_postfix_setup.html)
+- [Enabling replying via email](https://docs.gitlab.com/ee/administration/reply_by_email.html#set-it-up)
+  - [Installing and configuring postfix](https://docs.gitlab.com/ee/administration/reply_by_email_postfix_setup.html)
 - [Enabling container registry on GitLab](https://docs.gitlab.com/ee/administration/packages/container_registry.html#container-registry-domain-configuration)
   - You will require SSL certificates for the domain used for container registry
-- [Enabling GitLab Pages](https://docs.gitlab.com/ce/administration/pages/)
+- [Enabling GitLab Pages](https://docs.gitlab.com/ee/administration/pages/)
   - If you want HTTPS enabled, you will have to get wildcard certificates
 - [Enabling Elasticsearch](https://docs.gitlab.com/ee/integration/elasticsearch.html)
 - [GitLab Mattermost](gitlab-mattermost/README.md) Set up the Mattermost messaging app that ships with Omnibus GitLab package.
-- [GitLab Prometheus](https://docs.gitlab.com/ce/administration/monitoring/performance/prometheus.html) Set up the Prometheus
+- [GitLab Prometheus](https://docs.gitlab.com/ee/administration/monitoring/performance/prometheus.html) Set up the Prometheus
   monitoring included in the Omnibus GitLab package.
 - [GitLab High Availability Roles](roles/README.md)
@@ -84,11 +84,11 @@ to work best with the available resources. Check out the [documentation](setting
 - [Redis](settings/redis.md)
 - [Logs](settings/logs.md)
 - [Database](settings/database.md)
-- [Reply by email](https://docs.gitlab.com/ce/incoming_email/README.html)
+- [Reply by email](https://docs.gitlab.com/ee/incoming_email/README.html)
 - [Environment variables](settings/environment-variables.md)
 - [`gitlab.yml`](settings/gitlab.yml.md)
 - [Backups](settings/backups.md)
-- [Pages](https://docs.gitlab.com/ce/pages/administration.html)
+- [Pages](https://docs.gitlab.com/ee/pages/administration.html)
 - [SSL](settings/ssl.md)
 - [GitLab and Registry](architecture/registry/README.md)
 - [Configuring an asset proxy server](https://docs.gitlab.com/ee/security/asset_proxy.html)

doc/common_installation_problems/README.md

@@ -443,7 +443,7 @@ sudo chown -R git:git /var/opt/gitlab/gitlab-rails/tmp/cache
 ## 'Short read or OOM loading DB' error
-Try cleaning the old Redis session by following the [documentation here.](https://docs.gitlab.com/ce/operations/cleaning_up_redis_sessions.html)
+Try cleaning the old Redis session by following the [documentation here.](https://docs.gitlab.com/ee/operations/cleaning_up_redis_sessions.html)
 ## Apt error 'The requested URL returned error: 403'
@@ -514,7 +514,7 @@ how to override the default headers.
 ## Extension missing pg_trgm
-Starting from GitLab 8.6, [GitLab requires](https://docs.gitlab.com/ce/install/requirements.html#postgresql-requirements)
+Starting from GitLab 8.6, [GitLab requires](https://docs.gitlab.com/ee/install/requirements.html#postgresql-requirements)
 the PostgreSQL extension `pg_trgm`.
 If you are using Omnibus GitLab package with the bundled database, the extension
 should be automatically enabled when you upgrade.
@@ -574,7 +574,7 @@ above, and finally restart the container.
 ## Errno::ENOMEM: Cannot allocate memory during backup or upgrade
-[GitLab requires](https://docs.gitlab.com/ce/install/requirements.html#memory)
+[GitLab requires](https://docs.gitlab.com/ee/install/requirements.html#memory)
 2GB of available memory to run without errors. Having 2GB of memory installed may
 not be enough depending on the resource usage of other processes on your server.
 If GitLab runs fine when not upgrading or running a backup, then adding more swap
@@ -714,5 +714,5 @@ If using this configuration, runit service must be started before running
 [certificate link shell script]: https://gitlab.com/snippets/6285
 [script source]: https://www.madboa.com/geek/openssl/#verify-new
 [Change the default proxy headers section of nginx doc]: ../settings/nginx.md
-[reconfigure GitLab]: https://docs.gitlab.com/ce/administration/restart_gitlab.html#omnibus-gitlab-reconfigure
+[reconfigure GitLab]: https://docs.gitlab.com/ee/administration/restart_gitlab.html#omnibus-gitlab-reconfigure
 [runit-cookbook]: https://gitlab.com/gitlab-org/build/omnibus-mirror/runit-cookbook/blob/master/recipes/default.rb

doc/development/README.md

@@ -59,7 +59,7 @@ their applicability:
 1. Tests, as explained in [Writing Tests](#writing-tests)
 1. Documentation explaining the change
 1. If Merge Request introduces change in user facing configuration, update to [`gitlab.rb.template`](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/files/gitlab-config-template/gitlab.rb.template)
-1. [Changelog entry](https://docs.gitlab.com/ce/development/changelog.html) to inform about the change, if necessary.
+1. [Changelog entry](https://docs.gitlab.com/ee/development/changelog.html) to inform about the change, if necessary.
 **Note:** Ensure shared runners are enabled for your fork in order for our automated tests to run:

doc/docker/README.md

@@ -458,7 +458,7 @@ Here's an example that deploys GitLab with four runners as a [stack](https://doc
 The GitLab Docker images can also be deployed to various container scheduling platforms.
-- Kubernetes using the [GitLab Helm Charts](https://docs.gitlab.com/ce/install/kubernetes/).
+- Kubernetes using the [GitLab Helm Charts](https://docs.gitlab.com/ee/install/kubernetes/).
 - Mesosphere DC/OS using the [DC/OS Package](https://github.com/dcos/examples/tree/master/gitlab/1.8).
 - Docker Cloud using the [docker-compose config](#install-gitlab-using-docker-compose).

doc/gitlab-ci/README.md

@@ -2,4 +2,4 @@
 Starting with GitLab 8.0, GitLab CI is integrated into GitLab.
-To see how to configure your project with GitLab CI, see the [GitLab CI quickstart documentation](https://docs.gitlab.com/ce/ci/quick_start/README.html).
+To see how to configure your project with GitLab CI, see the [GitLab CI quickstart documentation](https://docs.gitlab.com/ee/ci/quick_start/README.html).

doc/maintenance/README.md

@@ -152,7 +152,7 @@ of removing unused tags. Currently, this is exposed using the API, but in the fu
 these controls will be migrated to the GitLab interface.
 Project maintainers can
-[delete Container Registry tags in bulk](https://docs.gitlab.com/ce/api/container_registry.html#delete-repository-tags-in-bulk)
+[delete Container Registry tags in bulk](https://docs.gitlab.com/ee/api/container_registry.html#delete-repository-tags-in-bulk)
 periodically based on their own criteria.
 However, this alone does not recycle data, it only unlinks tags from manifests

doc/package-information/omnibus_packages.md

@@ -108,7 +108,7 @@ what was noted above:
 This method is useful for organizations just getting started with containers and schedulers, and may not be ready for a more complex installation. This method is a great introduction, and will work well for smaller organizations.
-[GitLab Architecture Overview]: https://docs.gitlab.com/ce/development/architecture.html#gitlab-architecture-overview
+[GitLab Architecture Overview]: https://docs.gitlab.com/ee/development/architecture.html#gitlab-architecture-overview
 [rubygems]: https://gitlab.com/gitlab-org/gitlab-foss/blob/master/Gemfile.lock
 [non-bundled PG database]: https://docs.gitlab.com/omnibus/settings/database.html#using-a-non-packaged-postgresql-database-management-server
 [GitLab Docker image]: https://docs.gitlab.com/omnibus/docker/README.html#gitlab-docker-images

doc/settings/backups.md

@@ -77,7 +77,7 @@ lost/leaked/stolen together with the keys needed to decrypt it.
 ## Creating an application backup
 To create a backup of your repositories and GitLab metadata, follow the
-[backup create documentation](https://docs.gitlab.com/ce/raketasks/backup_restore.html#creating-a-backup-of-the-gitlab-system).
+[backup create documentation](https://docs.gitlab.com/ee/raketasks/backup_restore.html#creating-a-backup-of-the-gitlab-system).
 Backup create will store a tar file in `/var/opt/gitlab/backups`.
@@ -111,7 +111,7 @@ in order to have these backups persisted outside the container.
 ## Restoring an application backup
-See [backup restore documentation](https://docs.gitlab.com/ce/raketasks/backup_restore.html#restore-for-omnibus-installations).
+See [backup restore documentation](https://docs.gitlab.com/ee/raketasks/backup_restore.html#restore-for-omnibus-installations).
 ## Backup and restore using non-packaged database
@@ -119,7 +119,7 @@ If you are using non-packaged database see [documentation on using non-packaged
 ## Upload backups to remote (cloud) storage
-For details check [backup restore document of GitLab CE](https://docs.gitlab.com/ce/raketasks/backup_restore.html#uploading-backups-to-a-remote-cloud-storage).
+For details check [backup restore document of GitLab CE](https://docs.gitlab.com/ee/raketasks/backup_restore.html#uploading-backups-to-a-remote-cloud-storage).
 ## Manually manage backup directory

doc/settings/configuration.md

@@ -31,14 +31,14 @@ Run `sudo gitlab-ctl reconfigure` for the change to take effect.
 NOTE: **Note:**
 After you change the external URL, it is recommended that you also
-[invalidate the Markdown cache](https://docs.gitlab.com/ce/administration/invalidate_markdown_cache.html).
+[invalidate the Markdown cache](https://docs.gitlab.com/ee/administration/invalidate_markdown_cache.html).
 ## Configuring a relative URL for GitLab
 NOTE: **Note:**
 Relative URL support in Omnibus GitLab is **experimental** and was
 [introduced][590] in version 8.5. For source installations there is a
-[separate document](https://docs.gitlab.com/ce/install/relative_url.html).
+[separate document](https://docs.gitlab.com/ee/install/relative_url.html).
 ---
@@ -700,7 +700,7 @@ See [doc/settings/smtp.md](smtp.md).
 ## Omniauth (Google, Twitter, GitHub login)
-See [Omniauth documentation](https://docs.gitlab.com/ce/integration/omniauth.html).
+See [Omniauth documentation](https://docs.gitlab.com/ee/integration/omniauth.html).
 ## Adjusting Unicorn settings

doc/settings/database.md

@@ -431,7 +431,7 @@ Please note:
 **This upgrade requires downtime as the database must be down while the upgrade is being performed.
 The length of time depends on the size of your database.
 If you would rather avoid downtime, it is possible to upgrade to a new database using [Slony](http://www.slony.info/).
-Please see our [guide](https://docs.gitlab.com/ce/update/upgrading_postgresql_using_slony.html) on how to perform the upgrade.**
+Please see our [guide](https://docs.gitlab.com/ee/update/upgrading_postgresql_using_slony.html) on how to perform the upgrade.**
 Once you have confirmed that the the above checklist is satisfied,
 you can proceed.
@@ -615,7 +615,7 @@ or as a Postgres superuser:
 sudo gitlab-psql -d gitlabhq_production
 ```
-[rake-backup]: https://docs.gitlab.com/ce/raketasks/backup_restore.html#create-a-backup-of-the-gitlab-system "Backup raketask documentation"
-[Reconfigure GitLab]: https://docs.gitlab.com/ce/administration/restart_gitlab.html#omnibus-gitlab-reconfigure "Reconfigure GitLab"
-[rake-restore]: https://docs.gitlab.com/ce/raketasks/backup_restore.html#restore-a-previously-created-backup "Restore raketask documentation"
-[database requirements document]: https://docs.gitlab.com/ce/install/requirements.html#database
+[rake-backup]: https://docs.gitlab.com/ee/raketasks/backup_restore.html#create-a-backup-of-the-gitlab-system "Backup raketask documentation"
+[Reconfigure GitLab]: https://docs.gitlab.com/ee/administration/restart_gitlab.html#omnibus-gitlab-reconfigure "Reconfigure GitLab"
+[rake-restore]: https://docs.gitlab.com/ee/raketasks/backup_restore.html#restore-a-previously-created-backup "Restore raketask documentation"
+[database requirements document]: https://docs.gitlab.com/ee/install/requirements.html#database

doc/settings/grafana.md

@@ -76,7 +76,7 @@ can skip this section.
 To use GitLab as an OAuth provider so that users of your GitLab instance
 have access to Grafana:
-1. First, [create an application ID and secret](https://docs.gitlab.com/ce/integration/oauth_provider.html).
+1. First, [create an application ID and secret](https://docs.gitlab.com/ee/integration/oauth_provider.html).
 1. Set the callback URL based on your `external_url`. For example `https://gitlab.example.com/-/grafana/login/gitlab`.

doc/settings/ldap.md

@@ -122,7 +122,7 @@ EOS
 Run `sudo gitlab-ctl reconfigure` for the LDAP settings to take effect.
 For more information on LDAP Integration, check
-[GitLab CE LDAP Documentation](https://docs.gitlab.com/ce/integration/ldap.html) or
+[GitLab CE LDAP Documentation](https://docs.gitlab.com/ee/integration/ldap.html) or
 [GitLab EE LDAP Documentation](https://docs.gitlab.com/ee/integration/ldap.html)
 *Note*: If you are using pre GitLab 7.4 [configuration syntax like described in the old version README LDAP section](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/e65f026839594d54ad46a31a672d735b9caa16f0/README.md#setting-up-ldap-sign-in) be advised that it is deprecated.

doc/settings/logs.md

@@ -122,7 +122,7 @@ mattermost_nginx['log_format'] = 'my format string $foo $bar'
 Structured logs can be exported via JSON to be parsed by Elasticsearch,
 Splunk, or another log management system. Some components already write JSON logs
 by default (e.g. see [GitLab CE logging
-documentation](https://docs.gitlab.com/ce/administration/logs.html)),
+documentation](https://docs.gitlab.com/ee/administration/logs.html)),
 but until GitLab 12.0 other GitLab components may be using an
 unstructured format. To enable JSON logging for all GitLab components in
 versions prior to GitLab 12.0 add these lines to `/etc/gitlab/gitlab.rb` and

doc/settings/nginx.md

@@ -171,7 +171,7 @@ in `/etc/gitlab/gitlab.rb`:
  }
 ```
-Save the file and [reconfigure GitLab](https://docs.gitlab.com/ce/administration/restart_gitlab.html#omnibus-gitlab-reconfigure)
+Save the file and [reconfigure GitLab](https://docs.gitlab.com/ee/administration/restart_gitlab.html#omnibus-gitlab-reconfigure)
 for the changes to take effect.
 This way you can specify any header supported by NGINX you require.
@@ -202,7 +202,7 @@ By default, Omnibus GitLab will use the IP addresses in `real_ip_trusted_address
 as GitLab's trusted proxies, which will keep users from being listed as signed
 in from those IPs.
-Save the file and [reconfigure GitLab](https://docs.gitlab.com/ce/administration/restart_gitlab.html#omnibus-gitlab-reconfigure)
+Save the file and [reconfigure GitLab](https://docs.gitlab.com/ee/administration/restart_gitlab.html#omnibus-gitlab-reconfigure)
 for the changes to take effect.
 ## Configuring HTTP2 protocol
@@ -231,7 +231,7 @@ specifying in `/etc/gitlab/gitlab.rb`:
 nginx['http2_enabled'] = false
 ```
-Save the file and [reconfigure GitLab](https://docs.gitlab.com/ce/administration/restart_gitlab.html#omnibus-gitlab-reconfigure)
+Save the file and [reconfigure GitLab](https://docs.gitlab.com/ee/administration/restart_gitlab.html#omnibus-gitlab-reconfigure)
 for the changes to take effect.
 ## Using a non-bundled web-server

doc/settings/pages.md

-Documentation moved to <https://docs.gitlab.com/ce/pages/administration.html>.
+Documentation moved to <https://docs.gitlab.com/ee/pages/administration.html>.

doc/settings/redis.md

@@ -129,7 +129,7 @@ GitLab includes support for running with separate Redis instances for different
 ## Redis Sentinel
 For details on configuring Redis Sentinel, see
-<https://docs.gitlab.com/ce/administration/high_availability/redis.html>.
+<https://docs.gitlab.com/ee/administration/high_availability/redis.html>.
 ## Setting the Redis Cache instance as an LRU
@@ -149,7 +149,7 @@ redis['maxmemory_samples'] = 5
 ## Using a Redis HA setup
-See <https://docs.gitlab.com/ce/administration/high_availability/redis.html>.
+See <https://docs.gitlab.com/ee/administration/high_availability/redis.html>.
 ## Using Secure Sockets Layer (SSL)

doc/settings/ssl.md

@@ -16,7 +16,7 @@ Administrators can enable secure http using any method supported by a GitLab ser
 | Primary GitLab Instance Domain | [Yes](nginx.md#manually-configuring-https) | [Yes](#lets-encrypt-integration) |
 | Container Registry | [Yes](https://docs.gitlab.com/ee/administration/packages/container_registry.html#configure-container-registry-under-its-own-domain) | [Yes](#lets-encrypt-integration) |
 | Mattermost | [Yes](https://docs.gitlab.com/omnibus/gitlab-mattermost/README.html#running-gitlab-mattermost-with-https) | [Yes](#lets-encrypt-integration) |
-| GitLab Pages | [Yes](https://docs.gitlab.com/ce/administration/pages/#wildcard-domains-with-tls-support) | No |
+| GitLab Pages | [Yes](https://docs.gitlab.com/ee/administration/pages/#wildcard-domains-with-tls-support) | No |
 ### Let's Encrypt Integration

doc/update/convert_to_omnibus.md

@@ -109,6 +109,6 @@ to 12.1.
 To convert to PostgreSQL and use the built-in server, follow the steps:
-- [Create a backup of the non-Omnibus MySQL installation](https://docs.gitlab.com/ce/raketasks/backup_restore.html#creating-a-backup-of-the-gitlab-system)
+- [Create a backup of the non-Omnibus MySQL installation](https://docs.gitlab.com/ee/raketasks/backup_restore.html#creating-a-backup-of-the-gitlab-system)
 - [Export and convert the existing MySQL database in the GitLab backup file](https://docs.gitlab.com/ee/update/mysql_to_postgresql.html#converting-a-gitlab-backup-file-from-mysql-to-postgres)
-- [Restore this in the Omnibus installation](https://docs.gitlab.com/ce/raketasks/backup_restore.html#restore-for-omnibus-installations)
+- [Restore this in the Omnibus installation](https://docs.gitlab.com/ee/raketasks/backup_restore.html#restore-for-omnibus-installations)

files/gitlab-config-template/gitlab.rb.template

@@ -82,7 +82,7 @@ external_url 'GENERATED_EXTERNAL_URL'
 # gitlab_rails['gitlab_default_projects_features_container_registry'] = true
 ### Automatic issue closing
-###! See https://docs.gitlab.com/ce/customization/issue_closing.html for more
+###! See https://docs.gitlab.com/ee/customization/issue_closing.html for more
 ###! information about this pattern.
 # gitlab_rails['gitlab_issue_closing_pattern'] = "\b((?:[Cc]los(?:e[sd]?|ing)|\b[Ff]ix(?:e[sd]|ing)?|\b[Rr]esolv(?:e[sd]?|ing)|\b[Ii]mplement(?:s|ed|ing)?)(:?) +(?:(?:issues? +)?%{issue_ref}(?:(?:, *| +and +)?)|([A-Z][A-Z0-9_]+-\d+))+)"
@@ -100,7 +100,7 @@ external_url 'GENERATED_EXTERNAL_URL'
 ###! Periodically executed jobs, to self-heal Gitlab, do external
 ###! synchronizations, etc.
 ###! Docs: https://github.com/ondrejbartas/sidekiq-cron#adding-cron-job
-###!       https://docs.gitlab.com/ce/ci/yaml/README.html#artifacts:expire_in
+###!       https://docs.gitlab.com/ee/ci/yaml/README.html#artifacts:expire_in
 # gitlab_rails['stuck_ci_jobs_worker_cron'] = "0 0 * * *"
 # gitlab_rails['expire_build_artifacts_worker_cron'] = "50 * * * *"
 # gitlab_rails['pipeline_schedule_worker_cron'] = "19 * * * *"
@@ -162,7 +162,7 @@ external_url 'GENERATED_EXTERNAL_URL'
 ### Reply by email
 ###! Allow users to comment on issues and merge requests by replying to
 ###! notification emails.
-###! Docs: https://docs.gitlab.com/ce/administration/reply_by_email.html
+###! Docs: https://docs.gitlab.com/ee/administration/reply_by_email.html
 # gitlab_rails['incoming_email_enabled'] = true
 #### Incoming Email Address
@@ -349,7 +349,7 @@ external_url 'GENERATED_EXTERNAL_URL'
 # gitlab_rails['smartcard_san_extensions'] = false
 ### OmniAuth Settings
-###! Docs: https://docs.gitlab.com/ce/integration/omniauth.html
+###! Docs: https://docs.gitlab.com/ee/integration/omniauth.html
 # gitlab_rails['omniauth_enabled'] = nil
 # gitlab_rails['omniauth_allow_single_sign_on'] = ['saml']
 # gitlab_rails['omniauth_sync_email_from_provider'] = 'saml'
@@ -376,7 +376,7 @@ external_url 'GENERATED_EXTERNAL_URL'
 # gitlab_rails['manage_backup_path'] = true
 # gitlab_rails['backup_path'] = "/var/opt/gitlab/backups"
-###! Docs: https://docs.gitlab.com/ce/raketasks/backup_restore.html#backup-archive-permissions
+###! Docs: https://docs.gitlab.com/ee/raketasks/backup_restore.html#backup-archive-permissions
 # gitlab_rails['backup_archive_permissions'] = 0644
 # gitlab_rails['backup_pg_schema'] = 'public'
@@ -436,7 +436,7 @@ external_url 'GENERATED_EXTERNAL_URL'
 # gitlab_rails['gitaly_token'] = 'secret token'
 ### For storing GitLab application uploads, eg. LFS objects, build artifacts
-###! Docs: https://docs.gitlab.com/ce/development/shared_files.html
+###! Docs: https://docs.gitlab.com/ee/development/shared_files.html
 # gitlab_rails['shared_path'] = '/var/opt/gitlab/gitlab-rails/shared'
 ### Wait for file system to be mounted
@@ -572,7 +572,7 @@ external_url 'GENERATED_EXTERNAL_URL'
 ################################################################################
 ## Container Registry settings
-##! Docs: https://docs.gitlab.com/ce/administration/container_registry.html
+##! Docs: https://docs.gitlab.com/ee/administration/container_registry.html
 ################################################################################
 # registry_external_url 'https://registry.example.com'
@@ -618,7 +618,7 @@ external_url 'GENERATED_EXTERNAL_URL'
 # registry['compatibility_schema1_enabled'] = false
 ### Registry backend storage
-###! Docs: https://docs.gitlab.com/ce/administration/container_registry.html#container-registry-storage-driver
+###! Docs: https://docs.gitlab.com/ee/administration/container_registry.html#container-registry-storage-driver
 # registry['storage'] = {
 #   's3' => {
 #     'accesskey' => 'AKIAKIAKI',
@@ -998,7 +998,7 @@ external_url 'GENERATED_EXTERNAL_URL'
 ###! **To enable only Redis service in this machine, uncomment
 ###!   one of the lines below (choose master or slave instance types).**
 ###! Docs: https://docs.gitlab.com/omnibus/settings/redis.html
-###!       https://docs.gitlab.com/ce/administration/high_availability/redis.html
+###!       https://docs.gitlab.com/ee/administration/high_availability/redis.html
 # redis_master_role['enable'] = true
 # redis_slave_role['enable'] = true
@@ -1011,7 +1011,7 @@ external_url 'GENERATED_EXTERNAL_URL'
 ###! **You need a master slave Redis replication to be able to do failover**
 ###! **Please read the documentation before enabling it to understand the
 ###!   caveats:**
-###! Docs: https://docs.gitlab.com/ce/administration/high_availability/redis.html
+###! Docs: https://docs.gitlab.com/ee/administration/high_availability/redis.html
 ### Replication support
 #### Slave Redis instance
@@ -1264,7 +1264,7 @@ external_url 'GENERATED_EXTERNAL_URL'
 ################################################################################
 ## GitLab Pages
-##! Docs: https://docs.gitlab.com/ce/pages/administration.html
+##! Docs: https://docs.gitlab.com/ee/pages/administration.html
 ################################################################################
 ##! Define to enable GitLab Pages
@@ -1354,7 +1354,7 @@ external_url 'GENERATED_EXTERNAL_URL'
 ################################################################################
 ## GitLab CI
-##! Docs: https://docs.gitlab.com/ce/ci/quick_start/README.html
+##! Docs: https://docs.gitlab.com/ee/ci/quick_start/README.html
 ################################################################################
 # gitlab_ci['gitlab_ci_all_broken_builds'] = true
@@ -1447,12 +1447,12 @@ external_url 'GENERATED_EXTERNAL_URL'
 ################################################################################
 ## Prometheus
-##! Docs: https://docs.gitlab.com/ce/administration/monitoring/prometheus/
+##! Docs: https://docs.gitlab.com/ee/administration/monitoring/prometheus/
 ################################################################################
 ###! **To enable only Monitoring service in this machine, uncomment
 ###!   the line below.**
-###! Docs: https://docs.gitlab.com/ce/administration/high_availability
+###! Docs: https://docs.gitlab.com/ee/administration/high_availability
 # monitoring_role['enable'] = true
 # prometheus['enable'] = true
@@ -1543,7 +1543,7 @@ external_url 'GENERATED_EXTERNAL_URL'
 ################################################################################
 ## Prometheus Node Exporter
-##! Docs: https://docs.gitlab.com/ce/administration/monitoring/prometheus/node_exporter.html
+##! Docs: https://docs.gitlab.com/ee/administration/monitoring/prometheus/node_exporter.html
 ################################################################################
 # node_exporter['enable'] = true
@@ -1562,7 +1562,7 @@ external_url 'GENERATED_EXTERNAL_URL'
 ################################################################################
 ## Prometheus Redis exporter
-##! Docs: https://docs.gitlab.com/ce/administration/monitoring/prometheus/redis_exporter.html
+##! Docs: https://docs.gitlab.com/ee/administration/monitoring/prometheus/redis_exporter.html
 ################################################################################
 # redis_exporter['enable'] = true
@@ -1580,7 +1580,7 @@ external_url 'GENERATED_EXTERNAL_URL'
 ################################################################################
 ## Prometheus Postgres exporter
-##! Docs: https://docs.gitlab.com/ce/administration/monitoring/prometheus/postgres_exporter.html
+##! Docs: https://docs.gitlab.com/ee/administration/monitoring/prometheus/postgres_exporter.html
 ################################################################################
 # postgres_exporter['enable'] = true
@@ -1608,7 +1608,7 @@ external_url 'GENERATED_EXTERNAL_URL'
 ################################################################################
 ## Prometheus Gitlab exporter
-##! Docs: https://docs.gitlab.com/ce/administration/monitoring/prometheus/gitlab_exporter.html
+##! Docs: https://docs.gitlab.com/ee/administration/monitoring/prometheus/gitlab_exporter.html
 ################################################################################
@@ -1629,7 +1629,7 @@ external_url 'GENERATED_EXTERNAL_URL'
 ################################################################################
 ## Grafana Dashboards
-##! Docs: https://docs.gitlab.com/ce/administration/monitoring/prometheus/#prometheus-as-a-grafana-data-source
+##! Docs: https://docs.gitlab.com/ee/administration/monitoring/prometheus/#prometheus-as-a-grafana-data-source
 ################################################################################
 # grafana['enable'] = true
@@ -1892,7 +1892,7 @@ external_url 'GENERATED_EXTERNAL_URL'
 ##! To enable Sentinel and disable all other services in this machine,
 ##! uncomment the line below (if you've enabled Redis role, it will keep it).
-##! Docs: https://docs.gitlab.com/ce/administration/high_availability/redis.html
+##! Docs: https://docs.gitlab.com/ee/administration/high_availability/redis.html
 # redis_sentinel_role['enable'] = true
 # sentinel['enable'] = true