# HG changeset patch # User Marcel Amirault <mamirault@gitlab.com> # Date 1568885916 0 # Thu Sep 19 09:38:36 2019 +0000 # Node ID c044a1951835a2b28d9b5fe16bb8e9feeecdfdfb # Parent 521dd8fff402fb9d4d5a3d59049e4888213be68c Update links in omnibus The updated docs link tester found many redirected and broken links, and they were all updated in omnibus diff --git a/doc/common_installation_problems/README.md b/doc/common_installation_problems/README.md --- a/doc/common_installation_problems/README.md +++ b/doc/common_installation_problems/README.md @@ -18,7 +18,7 @@ sudo apt-get clean ``` -See [Joe Damato's from Packagecloud comment](https://gitlab.com/gitlab-org/omnibus-gitlab/issues/628#note_1824330) and [his blog article](http://blog.packagecloud.io/eng/2016/03/21/apt-hash-sum-mismatch/) for more context. +See [Joe Damato's from Packagecloud comment](https://gitlab.com/gitlab-org/omnibus-gitlab/issues/628#note_1824330) and [his blog article](https://blog.packagecloud.io/eng/2016/03/21/apt-hash-sum-mismatch/) for more context. Another workaround is to download the package manually by selecting the correct package from the [CE packages](https://packages.gitlab.com/gitlab/gitlab-ce) or [EE packages](https://packages.gitlab.com/gitlab/gitlab-ee) repository: @@ -299,7 +299,7 @@ This is unlikely to happen with non virtualized machines but on a VPS with virtualization like openVZ, container might not have the required module enabled or container doesn't have access to kernel parameters. -Try enabling the module on which sysctl errored out, on how to enable the module see example [here](http://serverfault.com/questions/477718/sysctl-p-etc-sysctl-conf-returns-error). +Try enabling the module on which sysctl errored out, on how to enable the module see example [here](https://serverfault.com/questions/477718/sysctl-p-etc-sysctl-conf-returns-error). There is a reported workaround described in [this issue](https://gitlab.com/gitlab-org/omnibus-gitlab/issues/361) which requires editing the GitLab' internal recipe by supplying the switch which will ignore failures. Ignoring errors can have unexpected side effects on performance of your GitLab server so it is not recommended to do so. @@ -461,7 +461,7 @@ PassThroughPattern: (packages\.gitlab\.com|packages-gitlab-com\.s3\.amazonaws\.com) ``` -Read more about `apt-cacher-ng` and the reasons why this change is needed [on the packagecloud blog](http://blog.packagecloud.io/eng/2015/05/05/using-apt-cacher-ng-with-ssl-tls/). +Read more about `apt-cacher-ng` and the reasons why this change is needed [on the packagecloud blog](https://blog.packagecloud.io/eng/2015/05/05/using-apt-cacher-ng-with-ssl-tls/). ## Using self signed certificate or custom certificate authorities @@ -715,4 +715,4 @@ [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 -[runit-cookbook]: https://gitlab.com/gitlab-org/omnibus-gitlab/tree/master/files/gitlab-cookbooks/runit/recipes/default.rb +[runit-cookbook]: https://gitlab.com/gitlab-org/build/omnibus-mirror/runit-cookbook/blob/master/recipes/default.rb diff --git a/doc/development/openshift/README.md b/doc/development/openshift/README.md --- a/doc/development/openshift/README.md +++ b/doc/development/openshift/README.md @@ -27,13 +27,13 @@ ### Minishift -Installation instructions for Minishift can be found at <https://docs.openshift.org/latest/minishift/getting-started/installing.html> +Installation instructions for Minishift can be found at <https://docs.okd.io/latest/minishift/getting-started/installing.html> 1. Before installing Minishift you need to install the proper docker machine driver. - - For Linux, install the [kvm driver](https://minishift.io/docs/docker-machine-drivers.html#kvm-driver) - - For Mac OSX, install the [xhyve driver](https://minishift.io/docs/docker-machine-drivers.html#xhyve-driver) + - For Linux, install the [kvm driver](https://docs.okd.io/latest/minishift/getting-started/setting-up-virtualization-environment.html#setting-up-kvm-driver) + - For Mac OSX, install the [xhyve driver](https://docs.okd.io/latest/minishift/getting-started/setting-up-virtualization-environment.html#setting-up-xhyve-driver) -1. Install Minishift, following the [instruction for your platform](https://docs.openshift.org/latest/minishift/getting-started/installing.html) +1. Install Minishift, following the [instruction for your platform](https://docs.okd.io/latest/minishift/getting-started/installing.html) 1. Start Minishift with enough cpu/memory to run GitLab: `minishift start --cpus 4 --memory 6144` - When it is finished starting, the command will output the location of the web console. @@ -45,7 +45,11 @@ ### Docker oc cluster up -If you have Docker installed, you can setup OpenShift Origin on your local machine: <https://github.com/openshift/origin/blob/master/docs/cluster_up_down.md> +NOTE: **Note:** +The information listed below may be out of date. See <https://docs.okd.io/latest/getting_started/administrators.html> +for more recent information regarding cluster setup. + +If you have Docker installed, you can setup OpenShift Origin on your local machine: <https://github.com/openshift/origin/blob/77bf0a926c045142570bb50a9a83086a370506a8/docs/cluster_up_down.md> `**Note:`this currently does not start if you are using docker-ce/ee with the new version scheme (17.xx) @@ -127,11 +131,11 @@ ### Production Ansible Installer -You can use OpenShift's Ansible installer to setup OpenShift masters and slaves in Digital Ocean. Follow the [advanced install docs](https://docs.openshift.org/latest/install_config/install/advanced_install.html). +You can use OpenShift's Ansible installer to set up OpenShift masters and slaves in Digital Ocean. Follow the [advanced install docs](https://docs.openshift.com/container-platform/3.7/install_config/install/advanced_install.html). You can find the Ansible playbooks at: <https://github.com/openshift/openshift-ansible> -After setting it all up, you will need to make sure you deploy the registry and router mentioned in the [what's next section](https://docs.openshift.org/latest/install_config/install/advanced_install.html#what-s-next) +After setting it all up, you will need to make sure you deploy the registry and router mentioned in the [what's next section](https://docs.openshift.com/container-platform/3.7/install_config/install/advanced_install.html#whats-next) In order to finish setting up the cluster, you need to create a project and allow your project's service account to run as anyuid. diff --git a/doc/development/public-attributes.md b/doc/development/public-attributes.md --- a/doc/development/public-attributes.md +++ b/doc/development/public-attributes.md @@ -20,7 +20,7 @@ end ``` -The file is generated as part of the [GitLabHander](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/files/gitlab-cookbooks/package/libraries/handers/gitlab.rb#L36). +The file is generated as part of the [GitLabHandler](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/files/gitlab-cookbooks/package/libraries/handlers/gitlab.rb#L36). ## Reading an entry from public_attributes.json from a `gitlab-ctl` command diff --git a/doc/docker/README.md b/doc/docker/README.md --- a/doc/docker/README.md +++ b/doc/docker/README.md @@ -161,8 +161,8 @@ ## After starting a container -After starting a container you can visit <http://localhost/> or -<http://192.168.59.103> if you use boot2docker. It might take a while before +After starting a container you can visit `http://localhost/` or +`http://192.168.59.103` if you use boot2docker. It might take a while before the Docker container starts to respond to queries. NOTE: **Note:** diff --git a/doc/gitlab-mattermost/README.md b/doc/gitlab-mattermost/README.md --- a/doc/gitlab-mattermost/README.md +++ b/doc/gitlab-mattermost/README.md @@ -226,14 +226,14 @@ For help and support around your GitLab Mattermost deployment please see: -- [Troubleshooting Forum](https://forum.mattermost.org/t/about-the-trouble-shooting-category/150/1) for configuration questions and issues -- [Troubleshooting FAQ](http://docs.mattermost.com/install/troubleshooting.html) +- [Troubleshooting Forum](https://forum.mattermost.org/t/how-to-use-the-troubleshooting-forum/150) for configuration questions and issues +- [Troubleshooting FAQ](https://docs.mattermost.com/install/troubleshooting.html) - [Mattermost GitLab Issues Support Handbook](https://docs.mattermost.com/process/support.html?highlight=omnibus#gitlab-issues) - [GitLab Mattermost issue tracker](https://gitlab.com/gitlab-org/gitlab-mattermost/issues) for verified bugs with repro steps ## Upgrading GitLab Mattermost -> Note: These upgrade instructions are for GitLab Version 8.9 (Mattermost v3.1.0) and above. For upgrading versions prior to GitLab 8.9, [additional steps are required](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc//gitlab-mattermost/README.md#upgrading-gitlab-mattermost-from-versions-prior-to-89). +> Note: These upgrade instructions are for GitLab Version 8.9 (Mattermost v3.1.0) and above. For upgrading versions prior to GitLab 8.9, [additional steps are required](#upgrading-gitlab-mattermost-from-versions-prior-to-89). Below is a list of Mattermost versions for GitLab 11.10 and later: @@ -404,11 +404,11 @@ ### Migrating Mattermost outside of GitLab -Follow the [Mattermost Migration Guide](http://docs.mattermost.com/administration/migrating.html) to move your Mattermost configuration settings and data to another directory or server independent from GitLab omnibus. +Follow the [Mattermost Migration Guide](https://docs.mattermost.com/administration/migrating.html) to move your Mattermost configuration settings and data to another directory or server independent from GitLab omnibus. ### Upgrading GitLab Mattermost outside of GitLab -If you choose to upgrade Mattermost outside of GitLab's omnibus automation, please [follow this guide](http://docs.mattermost.com/administration/upgrade-guide.html). +If you choose to upgrade Mattermost outside of GitLab's omnibus automation, please [follow this guide](https://docs.mattermost.com/administration/upgrade.html). ## Administering GitLab Mattermost @@ -447,7 +447,7 @@ The source code can be modified to support not only GitLab, but any in-house applications you may have that support webhooks. Also see: -- [Mattermost incoming webhook documentation](http://docs.mattermost.com/developer/webhooks-incoming.html) +- [Mattermost incoming webhook documentation](https://docs.mattermost.com/developer/webhooks-incoming.html) - [GitLab webhook documentation](https://docs.gitlab.com/ce/web_hooks/web_hooks.html)  diff --git a/doc/package-information/deprecated_os.md b/doc/package-information/deprecated_os.md --- a/doc/package-information/deprecated_os.md +++ b/doc/package-information/deprecated_os.md @@ -24,7 +24,7 @@ other OSs, openSUSE for example, that don't follow the LTS concept. Hence to avoid confusion, the official policy is that at any point of time, all the operating systems supported by GitLab are listed in the [installation -page](https://about.gitlab.com/installation). +page](https://about.gitlab.com/install/). The following lists the currently supported OSs and their possible EOL dates. diff --git a/doc/release/README.md b/doc/release/README.md --- a/doc/release/README.md +++ b/doc/release/README.md @@ -137,7 +137,7 @@ ### Updating cloud images -The cloud image release process is documented here: <https://about.gitlab.com/cloud-images/>. +The cloud image release process is documented here: <https://about.gitlab.com/handbook/alliances/cloud-images/>. New image are released when: diff --git a/doc/settings/database.md b/doc/settings/database.md --- a/doc/settings/database.md +++ b/doc/settings/database.md @@ -431,7 +431,7 @@ **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](http://docs.gitlab.com/ce/update/upgrading_postgresql_using_slony.html) on how to perform the upgrade.** +Please see our [guide](https://docs.gitlab.com/ce/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. diff --git a/doc/settings/grafana.md b/doc/settings/grafana.md --- a/doc/settings/grafana.md +++ b/doc/settings/grafana.md @@ -112,7 +112,7 @@ gitlab-ctl set-grafana-password ``` -See the [Grafana CLI documentation](http://docs.grafana.org/administration/cli/#reset-admin-password) +See the [Grafana CLI documentation](https://grafana.com/docs/administration/cli/#reset-admin-password) for more information. ## Dashboards diff --git a/doc/settings/nginx.md b/doc/settings/nginx.md --- a/doc/settings/nginx.md +++ b/doc/settings/nginx.md @@ -366,7 +366,7 @@ (e.g. "422 Unprocessable Entity", "Can't verify CSRF token authenticity") if you forget this step. For more information, see: -- <http://stackoverflow.com/questions/16042647/whats-the-de-facto-standard-for-a-reverse-proxy-to-tell-the-backend-ssl-is-used> +- <https://stackoverflow.com/questions/16042647/whats-the-de-facto-standard-for-a-reverse-proxy-to-tell-the-backend-ssl-is-used> - <https://websiteforstudents.com/setup-apache2-reverse-proxy-nginx-ubuntu-17-04-17-10/> ## Setting HTTP Strict Transport Security diff --git a/doc/settings/redis.md b/doc/settings/redis.md --- a/doc/settings/redis.md +++ b/doc/settings/redis.md @@ -44,12 +44,12 @@ issues) for use with GitLab you can do so using GitLab Omnibus. > **Note:** Redis does not require authentication by default. See -> [Redis Security](http://redis.io/topics/security) documentation for more +> [Redis Security](https://redis.io/topics/security) documentation for more > information. We recommend using a combination of a Redis password and tight > firewall rules to secure your Redis service. 1. Download/install GitLab Omnibus using **steps 1 and 2** from - [GitLab downloads](https://about.gitlab.com/downloads). Do not complete other + [GitLab downloads](https://about.gitlab.com/install/). Do not complete other steps on the download page. 1. Create/edit `/etc/gitlab/gitlab.rb` and use the following configuration. Be sure to change the `external_url` to match your eventual GitLab front-end diff --git a/doc/settings/ssl.md b/doc/settings/ssl.md --- a/doc/settings/ssl.md +++ b/doc/settings/ssl.md @@ -292,7 +292,7 @@ GitLab-Omnibus manages custom certificates by symlinking any certificate that gets added to `/etc/gitlab/trusted-certs/` to `/opt/gitlab/embedded/ssl/certs` -using the [c_rehash](https://www.openssl.org/docs/man1.1.0/apps/c_rehash.html) +using the [c_rehash](https://www.openssl.org/docs/man1.1.0/man1/c_rehash.html) tool. For example, let's suppose we add `customcacert.pem` to `/etc/gitlab/trusted-certs/`: diff --git a/doc/update/README.md b/doc/update/README.md --- a/doc/update/README.md +++ b/doc/update/README.md @@ -36,8 +36,8 @@ ### Updating using the official repositories -If you have installed Omnibus GitLab [Community Edition](https://about.gitlab.com/installation/?version=ce#) -or [Enterprise Edition](https://about.gitlab.com/installation), then the +If you have installed Omnibus GitLab [Community Edition](https://about.gitlab.com/install/?version=ce) +or [Enterprise Edition](https://about.gitlab.com/install/), then the official GitLab repository should have already been set up for you. To update to a newer GitLab version, all you have to do is: @@ -459,7 +459,7 @@ See example below: -First download a GitLab 6.x.x [CE](https://about.gitlab.com/downloads/archives/) or +First download a GitLab 6.x.x [CE](https://packages.gitlab.com/gitlab/gitlab-ce) or [EE (subscribers only)](https://gitlab.com/subscribers/gitlab-ee/blob/master/doc/install/packages.md) package. diff --git a/doc/update/gitlab_11_changes.md b/doc/update/gitlab_11_changes.md --- a/doc/update/gitlab_11_changes.md +++ b/doc/update/gitlab_11_changes.md @@ -103,7 +103,7 @@ ### 11.6 -1. [Sidekiq probe of GitLab Monitor](https://docs.gitlab.com/ee/administration/monitoring/prometheus/gitlab_monitor_exporter.html) +1. [Sidekiq probe of GitLab Monitor](https://docs.gitlab.com/ee/administration/monitoring/prometheus/gitlab_exporter.html) will be disabled by default if GitLab is configured in [Redis HA mode](https://docs.gitlab.com/ee/administration/high_availability/redis.html). To manually enable it, users can set `gitlab_monitor['probe_sidekiq'] = true` in `/etc/gitlab/gitlab.rb` file. However, when manually enabling it in Redis diff --git a/doc/update/package_signatures.md b/doc/update/package_signatures.md --- a/doc/update/package_signatures.md +++ b/doc/update/package_signatures.md @@ -45,7 +45,7 @@ ### Enable Automatic Verification -The `rpm` tool and related package managers (`yum`,`zypper`) directly support the automatic verification of packages without intervention. If you used the automated repository configuration script after signed packages became available, then you will have no additional steps required. If you installed prior to the release of signed packages, you can either make the necessary changes, or re-run the automatic repository configuration script as found on the [Installation][install] page. +The `rpm` tool and related package managers (`yum`,`zypper`) directly support the automatic verification of packages without intervention. If you used the automated repository configuration script after signed packages became available, then you will have no additional steps required. If you installed prior to the release of signed packages, you can either make the necessary changes, or re-run the automatic repository configuration script as found on the [Installation](https://about.gitlab.com/install/) page. #### Yum (RedHat, CentOS) @@ -155,5 +155,3 @@ To make use of `debsig-verify`, perform the steps in [Configuring debsigs](#configuring-debsigs) and install the `debsig-verify` package. `debsig-verify gitlab-xxx.deb` - -[install]: https://about.gitlab.com/installation/