Commit 3f95dd16 authored by Marcel Amirault's avatar Marcel Amirault

Merge branch '276200-docs-administration-curl-double-quote' into 'master'

Docs: double quote cURL URLs in /docs/administration/

See merge request gitlab-org/gitlab!49445
parents 3a4b5218 1b8f8a6b
......@@ -77,7 +77,7 @@ Identify any existing health issues in the cluster by running the following comm
within each node. The command will return an empty array if the cluster is healthy:
```shell
curl http://127.0.0.1:8500/v1/health/state/critical
curl "http://127.0.0.1:8500/v1/health/state/critical"
```
Consul nodes communicate using the raft protocol. If the current leader goes
......
......@@ -151,7 +151,7 @@ There is an [issue where support is being discussed](https://gitlab.com/gitlab-o
##
## Public address
##
echo "External address: $(curl --silent ipinfo.io/ip)"
echo "External address: $(curl --silent "ipinfo.io/ip")"
```
In most cases, the following addresses will be used to configure GitLab
......
......@@ -19,5 +19,5 @@ be done by [changing the application settings through
the API](../api/settings.md#change-application-settings):
```shell
curl --request PUT --header "PRIVATE-TOKEN: <your_access_token>" https://gitlab.example.com/api/v4/application/settings?local_markdown_version=<increased_number>
curl --request PUT --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/application/settings?local_markdown_version=<increased_number>"
```
......@@ -139,7 +139,7 @@ the database. The following instructions can be used to build OpenSSH 7.5:
```shell
sudo su -
cd /tmp
curl --remote-name https://cdn.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-7.5p1.tar.gz
curl --remote-name "https://cdn.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-7.5p1.tar.gz"
tar xzvf openssh-7.5p1.tar.gz
yum install rpm-build gcc make wget openssl-devel krb5-devel pam-devel libX11-devel xmkmf libXt-devel
```
......
......@@ -1155,8 +1155,8 @@ After adding the setting, [reconfigure GitLab](../restart_gitlab.md#omnibus-gitl
Use curl to request debug output from the debug server:
```shell
curl localhost:5001/debug/health
curl localhost:5001/debug/vars
curl "localhost:5001/debug/health"
curl "localhost:5001/debug/vars"
```
### Advanced Troubleshooting
......@@ -1236,7 +1236,7 @@ mitmproxy --port 9000
This command runs mitmproxy on port `9000`. In another window, run:
```shell
curl --proxy http://localhost:9000 https://httpbin.org/status/200
curl --proxy "http://localhost:9000" "https://httpbin.org/status/200"
```
If everything is set up correctly, information is displayed on the mitmproxy window and
......
......@@ -434,13 +434,13 @@ If the monitoring node is not receiving any data, check that the exporters are
capturing data.
```shell
curl http[s]://localhost:<EXPORTER LISTENING PORT>/metric
curl "http[s]://localhost:<EXPORTER LISTENING PORT>/metric"
```
or
```shell
curl http[s]://localhost:<EXPORTER LISTENING PORT>/-/metric
curl "http[s]://localhost:<EXPORTER LISTENING PORT>/-/metric"
```
## Troubleshooting PgBouncer
......
......@@ -64,11 +64,11 @@ The process to set the snippets size limit through the Application Settings API
exactly the same as you would do to [update any other setting](../../api/settings.md#change-application-settings).
```shell
curl --request PUT --header "PRIVATE-TOKEN: <your_access_token>" https://gitlab.example.com/api/v4/application/settings?snippet_size_limit=52428800
curl --request PUT --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/application/settings?snippet_size_limit=52428800"
```
You can also use the API to [retrieve the current value](../../api/settings.md#get-current-application-settings).
```shell
curl --header "PRIVATE-TOKEN: <your_access_token>" https://gitlab.example.com/api/v4/application/settings
curl --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/application/settings"
```
......@@ -303,7 +303,7 @@ nslookup example.com 1.1.1.1
whois <ip_address> | grep -i "orgname\|netname"
# Curl headers with redirect
curl --head --location https://example.com
curl --head --location "https://example.com"
```
## Package Management
......
......@@ -24,7 +24,7 @@ following issues:
- `curl` fails:
```shell
curl https://gitlab.domain.tld
curl "https://gitlab.domain.tld"
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.haxx.se/docs/sslcerts.html
```
......@@ -125,7 +125,7 @@ The cause of the issue can be confirmed by checking if:
- `curl` fails:
```shell
$ curl https://gitlab.domain.tld
$ curl "https://gitlab.domain.tld"
curl: (60) SSL certificate problem: self signed certificate
More details here: https://curl.haxx.se/docs/sslcerts.html
```
......
......@@ -103,7 +103,7 @@ docker run -d --name elasticsearch \
docker.elastic.co/elasticsearch/elasticsearch:5.5.1
```
Then confirm it works in the browser at `curl http://<IP_ADDRESS>:9200/_cat/health`.
Then confirm it works in the browser at `curl "http://<IP_ADDRESS>:9200/_cat/health"`.
Elasticsearch's default username is `elastic` and password is `changeme`.
### Kroki
......
......@@ -59,7 +59,7 @@ interested in.
If you're using `curl` then you can use the verbose option to show request and response headers, as well as other debug info.
```shell
➜ ~ curl --verbose https://gitlab.example.com/api/v4/projects
➜ ~ curl --verbose "https://gitlab.example.com/api/v4/projects"
# look for a line that looks like this
< x-request-id: 4rAMkV3gof4
```
......
......@@ -65,11 +65,11 @@ The process to set the wiki page size limit through the Application Settings API
exactly the same as you would do to [update any other setting](../../api/settings.md#change-application-settings).
```shell
curl --request PUT --header "PRIVATE-TOKEN: <your_access_token>" https://gitlab.example.com/api/v4/application/settings?wiki_page_max_content_bytes=52428800
curl --request PUT --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/application/settings?wiki_page_max_content_bytes=52428800"
```
You can also use the API to [retrieve the current value](../../api/settings.md#get-current-application-settings).
```shell
curl --header "PRIVATE-TOKEN: <your_access_token>" https://gitlab.example.com/api/v4/application/settings
curl --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/application/settings"
```
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