Merge branch 'docs/https-many-docs-links' into 'master'
Https many links in docs See merge request gitlab-org/gitlab-ce!29776
This commit is contained in:
commit
6d68a3a254
|
@ -64,4 +64,4 @@ instructions](https://docs.gitlab.com/omnibus/settings/environment-variables.htm
|
|||
|
||||
It's possible to preconfigure the GitLab docker image by adding the environment
|
||||
variable `GITLAB_OMNIBUS_CONFIG` to the `docker run` command.
|
||||
For more information see the ['preconfigure-docker-container' section in the Omnibus documentation](http://docs.gitlab.com/omnibus/docker/#preconfigure-docker-container).
|
||||
For more information see the ['preconfigure-docker-container' section in the Omnibus documentation](https://docs.gitlab.com/omnibus/docker/#preconfigure-docker-container).
|
||||
|
|
|
@ -111,7 +111,7 @@ deploy the bundled PostgreSQL.
|
|||
> - If you are a Community Edition or Starter user, consider using a cloud hosted solution.
|
||||
> - This document will not cover installations from source.
|
||||
>
|
||||
> - If HA setup is not what you were looking for, see the [database configuration document](http://docs.gitlab.com/omnibus/settings/database.html)
|
||||
> - If HA setup is not what you were looking for, see the [database configuration document](https://docs.gitlab.com/omnibus/settings/database.html)
|
||||
> for the Omnibus GitLab packages.
|
||||
>
|
||||
> Please read this document fully before attempting to configure PostgreSQL HA
|
||||
|
@ -1146,7 +1146,7 @@ postgresql['trust_auth_cidr_addresses'] = %w(123.123.123.123/32 <other_cidrs>)
|
|||
If you're running into an issue with a component not outlined here, be sure to check the troubleshooting section of their specific documentation page.
|
||||
|
||||
- [Consul](consul.md#troubleshooting)
|
||||
- [PostgreSQL](http://docs.gitlab.com/omnibus/settings/database.html#troubleshooting)
|
||||
- [PostgreSQL](https://docs.gitlab.com/omnibus/settings/database.html#troubleshooting)
|
||||
- [GitLab application](gitlab.md#troubleshooting)
|
||||
|
||||
## Configure using Omnibus
|
||||
|
|
|
@ -66,7 +66,7 @@
|
|||
gitlab_rails['redis_port'] = '6379'
|
||||
gitlab_rails['redis_host'] = '10.1.0.6' # IP/hostname of Redis server
|
||||
gitlab_rails['redis_password'] = 'Redis Password'
|
||||
|
||||
|
||||
# Ensure UIDs and GIDs match between servers for permissions via NFS
|
||||
user['uid'] = 9000
|
||||
user['gid'] = 9000
|
||||
|
@ -81,11 +81,11 @@
|
|||
servers should point to the external url that users will use to access GitLab.
|
||||
In a typical HA setup, this will be the url of the load balancer which will
|
||||
route traffic to all GitLab application servers in the HA cluster.
|
||||
>
|
||||
>
|
||||
> **Note:** When you specify `https` in the `external_url`, as in the example
|
||||
above, GitLab assumes you have SSL certificates in `/etc/gitlab/ssl/`. If
|
||||
certificates are not present, Nginx will fail to start. See
|
||||
[Nginx documentation](http://docs.gitlab.com/omnibus/settings/nginx.html#enable-https)
|
||||
[Nginx documentation](https://docs.gitlab.com/omnibus/settings/nginx.html#enable-https)
|
||||
for more information.
|
||||
>
|
||||
> **Note:** It is best to set the `uid` and `gid`s prior to the initial reconfigure of GitLab. Omnibus will not recursively `chown` directories if set after the initial reconfigure.
|
||||
|
|
|
@ -235,4 +235,4 @@ Read more on high-availability configuration:
|
|||
1. [Configure the GitLab application servers](gitlab.md)
|
||||
1. [Configure the load balancers](load_balancer.md)
|
||||
|
||||
[udp-log-shipping]: http://docs.gitlab.com/omnibus/settings/logs.html#udp-log-shipping-gitlab-enterprise-edition-only "UDP log shipping"
|
||||
[udp-log-shipping]: https://docs.gitlab.com/omnibus/settings/logs.html#udp-log-shipping-gitlab-enterprise-edition-only "UDP log shipping"
|
||||
|
|
|
@ -4,7 +4,7 @@ GitLab has an advanced log system where everything is logged so that you
|
|||
can analyze your instance using various system log files. In addition to
|
||||
system log files, GitLab Enterprise Edition comes with Audit Events.
|
||||
Find more about them [in Audit Events
|
||||
documentation](http://docs.gitlab.com/ee/administration/audit_events.html)
|
||||
documentation](https://docs.gitlab.com/ee/administration/audit_events.html)
|
||||
|
||||
System log files are typically plain text in a standard log file format.
|
||||
This guide talks about how to read and use these system log files.
|
||||
|
|
|
@ -62,7 +62,7 @@ It will check that each component was set up according to the installation guide
|
|||
You may also have a look at our Troubleshooting Guides:
|
||||
|
||||
- [Troubleshooting Guide (GitLab)](http://docs.gitlab.com/ee/README.html#troubleshooting)
|
||||
- [Troubleshooting Guide (Omnibus Gitlab)](http://docs.gitlab.com/omnibus/README.html#troubleshooting)
|
||||
- [Troubleshooting Guide (Omnibus Gitlab)](https://docs.gitlab.com/omnibus/README.html#troubleshooting)
|
||||
|
||||
**Omnibus Installation**
|
||||
|
||||
|
|
|
@ -482,8 +482,8 @@ To define which should be used, the GitLab Runner process reads the configuratio
|
|||
If the `--user` flag is provided to run the GitLab Runner child processes as unprivileged user,
|
||||
the home directory of the main GitLab Runner process user will be used.
|
||||
|
||||
NOTE: **Note:**
|
||||
GitLab Runner reads this configuration **only** from `config.toml` and ignores it if
|
||||
NOTE: **Note:**
|
||||
GitLab Runner reads this configuration **only** from `config.toml` and ignores it if
|
||||
it's provided as an environment variable. This is because GitLab Runnner uses **only**
|
||||
`config.toml` configuration and doesn't interpolate **ANY** environment variables at
|
||||
runtime.
|
||||
|
@ -577,7 +577,7 @@ To configure credentials store, follow these steps:
|
|||
Make sure helper program is available in GitLab Runner `$PATH`.
|
||||
|
||||
1. Make GitLab Runner use it. There are two ways to accomplish this. Either:
|
||||
- Create a
|
||||
- Create a
|
||||
[variable](../variables/README.md#gitlab-cicd-environment-variables)
|
||||
`DOCKER_AUTH_CONFIG` with the content of the
|
||||
Docker configuration file as the value:
|
||||
|
@ -741,7 +741,7 @@ creation.
|
|||
[tutum/wordpress]: https://hub.docker.com/r/tutum/wordpress/
|
||||
[postgres-hub]: https://hub.docker.com/r/_/postgres/
|
||||
[mysql-hub]: https://hub.docker.com/r/_/mysql/
|
||||
[runner-priv-reg]: http://docs.gitlab.com/runner/configuration/advanced-configuration.html#using-a-private-container-registry
|
||||
[runner-priv-reg]: https://docs.gitlab.com/runner/configuration/advanced-configuration.html#using-a-private-container-registry
|
||||
[entrypoint]: https://docs.docker.com/engine/reference/builder/#entrypoint
|
||||
[cmd]: https://docs.docker.com/engine/reference/builder/#cmd
|
||||
[register]: https://docs.gitlab.com/runner/register/
|
||||
|
|
|
@ -418,9 +418,9 @@ You can find the IP address of a Runner for a specific project by:
|
|||
|
||||
![specific Runner IP address](img/specific_runner_ip_address.png)
|
||||
|
||||
[install]: http://docs.gitlab.com/runner/install/
|
||||
[install]: https://docs.gitlab.com/runner/install/
|
||||
[fifo]: https://en.wikipedia.org/wiki/FIFO_(computing_and_electronics)
|
||||
[register]: http://docs.gitlab.com/runner/register/
|
||||
[register]: https://docs.gitlab.com/runner/register/
|
||||
[protected branches]: ../../user/project/protected_branches.md
|
||||
[protected tags]: ../../user/project/protected_tags.md
|
||||
[project defined timeout]: ../../user/project/pipelines/settings.html#timeout
|
||||
|
|
|
@ -283,7 +283,7 @@ For instance, for `https://docs.gitlab.com/ce/user/index.html`,
|
|||
#### Default URL
|
||||
|
||||
The default and canonical URL for GitLab documentation is
|
||||
`http://docs.gitlab.com/ee/`, thus, all links
|
||||
`https://docs.gitlab.com/ee/`, thus, all links
|
||||
in the docs site should link to `/ee/` except when linking
|
||||
among `/ce/` docs themselves.
|
||||
|
||||
|
|
|
@ -710,7 +710,7 @@ for the changes to take effect.
|
|||
|
||||
If the document you are editing resides in a place other than the GitLab CE/EE
|
||||
`doc/` directory, instead of the relative link, use the full path:
|
||||
`http://docs.gitlab.com/ce/administration/restart_gitlab.html`.
|
||||
`https://docs.gitlab.com/ce/administration/restart_gitlab.html`.
|
||||
Replace `reconfigure` with `restart` where appropriate.
|
||||
|
||||
### Installation guide
|
||||
|
@ -962,6 +962,6 @@ curl --request PUT --header "PRIVATE-TOKEN: <your_access_token>" --data "domain_
|
|||
|
||||
[cURL]: http://curl.haxx.se/ "cURL website"
|
||||
[single spaces]: http://www.slate.com/articles/technology/technology/2011/01/space_invaders.html
|
||||
[gfm]: http://docs.gitlab.com/ce/user/markdown.html#newlines "GitLab flavored markdown documentation"
|
||||
[gfm]: https://docs.gitlab.com/ce/user/markdown.html#newlines "GitLab flavored markdown documentation"
|
||||
[ce-1242]: https://gitlab.com/gitlab-org/gitlab-ce/issues/1242
|
||||
[doc-restart]: ../../administration/restart_gitlab.md "GitLab restart documentation"
|
||||
|
|
|
@ -123,7 +123,7 @@ To disable the relative URL:
|
|||
1. Follow the same as above starting from 2. and set up the
|
||||
GitLab URL to one that doesn't contain a relative path.
|
||||
|
||||
[omnibus-rel]: http://docs.gitlab.com/omnibus/settings/configuration.html#configuring-a-relative-url-for-gitlab "How to set up relative URL in Omnibus GitLab"
|
||||
[omnibus-rel]: https://docs.gitlab.com/omnibus/settings/configuration.html#configuring-a-relative-url-for-gitlab "How to set up relative URL in Omnibus GitLab"
|
||||
[restart gitlab]: ../administration/restart_gitlab.md#installations-from-source "How to restart GitLab"
|
||||
|
||||
<!-- ## Troubleshooting
|
||||
|
|
|
@ -55,7 +55,7 @@ at Super User also has relevant information.
|
|||
|
||||
**Omnibus Trusted Chain**
|
||||
|
||||
[Install the self signed certificate or custom certificate authorities](http://docs.gitlab.com/omnibus/common_installation_problems/README.html#using-self-signed-certificate-or-custom-certificate-authorities)
|
||||
[Install the self signed certificate or custom certificate authorities](https://docs.gitlab.com/omnibus/common_installation_problems/README.html#using-self-signed-certificate-or-custom-certificate-authorities)
|
||||
in to GitLab Omnibus.
|
||||
|
||||
It is enough to concatenate the certificate to the main trusted certificate
|
||||
|
@ -71,4 +71,4 @@ After that restart GitLab with:
|
|||
sudo gitlab-ctl restart
|
||||
```
|
||||
|
||||
[jenkins]: http://docs.gitlab.com/ee/integration/jenkins.html
|
||||
[jenkins]: https://docs.gitlab.com/ee/integration/jenkins.html
|
||||
|
|
|
@ -43,4 +43,4 @@ Install and update your GitLab installation.
|
|||
|
||||
- [Install GitLab](https://about.gitlab.com/installation/)
|
||||
- [Update GitLab](https://about.gitlab.com/update/)
|
||||
- [Explore Omnibus GitLab configuration options](http://docs.gitlab.com/omnibus/settings/configuration.html)
|
||||
- [Explore Omnibus GitLab configuration options](https://docs.gitlab.com/omnibus/settings/configuration.html)
|
||||
|
|
|
@ -34,7 +34,7 @@ This section contains the following topics:
|
|||
|
||||
## Additional Resources
|
||||
|
||||
1. [GitLab Documentation](http://docs.gitlab.com)
|
||||
1. [GitLab Documentation](https://docs.gitlab.com)
|
||||
1. [GUI Clients](http://git-scm.com/downloads/guis)
|
||||
1. [Pro Git book](http://git-scm.com/book)
|
||||
1. [Platzi Course](https://courses.platzi.com/courses/git-gitlab/)
|
||||
|
|
|
@ -146,7 +146,7 @@ possible.
|
|||
- [Upgrading PostgreSQL Using Slony](upgrading_postgresql_using_slony.md), for
|
||||
upgrading a PostgreSQL database with minimal downtime.
|
||||
|
||||
[omnidocker]: http://docs.gitlab.com/omnibus/docker/README.html
|
||||
[omnidocker]: https://docs.gitlab.com/omnibus/docker/README.html
|
||||
[old-ee-upgrade-docs]: https://gitlab.com/gitlab-org/gitlab-ee/tree/11-8-stable-ee/doc/update
|
||||
[old-ce-upgrade-docs]: https://gitlab.com/gitlab-org/gitlab-ce/tree/11-8-stable/doc/update
|
||||
[source-ce-to-ee]: upgrading_from_ce_to_ee.md
|
||||
|
|
|
@ -24,7 +24,7 @@ to the webhook URL.
|
|||
|
||||
In most cases, you'll need to set up your own [webhook receiver](#example-webhook-receiver)
|
||||
to receive information from GitLab, and send it to another app, according to your needs.
|
||||
We already have a [built-in receiver](http://docs.gitlab.com/ce/project_services/slack.html)
|
||||
We already have a [built-in receiver](https://docs.gitlab.com/ce/project_services/slack.html)
|
||||
for sending [Slack](https://api.slack.com/incoming-webhooks) notifications _per project_.
|
||||
|
||||
## Overview
|
||||
|
@ -326,7 +326,7 @@ X-Gitlab-Event: Issue Hook
|
|||
"current": 1
|
||||
},
|
||||
"updated_at": {
|
||||
"previous": "2017-09-15 16:50:55 UTC",
|
||||
"previous": "2017-09-15 16:50:55 UTC",
|
||||
"current": "2017-09-15 16:52:00 UTC"
|
||||
},
|
||||
"labels": {
|
||||
|
@ -888,7 +888,7 @@ X-Gitlab-Event: Merge Request Hook
|
|||
"current": 1
|
||||
},
|
||||
"updated_at": {
|
||||
"previous": "2017-09-15 16:50:55 UTC",
|
||||
"previous": "2017-09-15 16:50:55 UTC",
|
||||
"current":"2017-09-15 16:52:00 UTC"
|
||||
},
|
||||
"labels": {
|
||||
|
|
|
@ -180,6 +180,6 @@ for details about the pipelines security model.
|
|||
[ce-4892]: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/4892 "Allow developers to merge into a protected branch without having push access"
|
||||
[ce-5081]: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5081 "Allow creating protected branches that can't be pushed to"
|
||||
[ce-21393]: https://gitlab.com/gitlab-org/gitlab-ce/issues/21393
|
||||
[ee-restrict]: http://docs.gitlab.com/ee/user/project/protected_branches.html#restricting-push-and-merge-access-to-certain-users
|
||||
[ee-restrict]: https://docs.gitlab.com/ee/user/project/protected_branches.html#restricting-push-and-merge-access-to-certain-users
|
||||
[perm]: ../permissions.md
|
||||
[ee]: https://about.gitlab.com/pricing/
|
||||
|
|
Loading…
Reference in New Issue