Skip to content

Commit 2e999bd

Browse files
authored
argo shell style (#237)
1 parent fc7762c commit 2e999bd

File tree

3 files changed

+7
-3
lines changed

3 files changed

+7
-3
lines changed

products/argo-tunnel/src/content/configuration/arguments.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ order: 1
99
All tunnel-related commands are prefixed with `tunnel`. For example:
1010

1111
```sh
12-
$ cloudflared tunnel --url localhost:5555 --hostname x.example.com`
12+
$ cloudflared tunnel --url localhost:5555 --hostname x.example.com
1313
```
1414

1515
- [Tunnel commands](#tunnel-commands)

products/argo-tunnel/src/content/getting-started/setup.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,9 @@ Follow these steps to set up Cloudflare Argo Tunnel:
1616

1717
1. Authenticate your instance `cloudflared` by logging in to your Cloudflare account with the following command:
1818

19-
`cloudflared tunnel login`
19+
```sh
20+
$ cloudflared tunnel login
21+
```
2022

2123
2. The command will attempt to open a browser and prompt you to authenticate with your Cloudflare account.
2224

products/argo-tunnel/src/content/routing-to-tunnel/dns.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,9 @@ You can create DNS records from `cloudflared`, which will provision a CNAME reco
3737

3838
To do so, run the following command.
3939

40-
`cloudflared tunnel route dns <UUID or NAME> www.app.com`
40+
```sh
41+
$ cloudflared tunnel route dns <UUID or NAME> www.app.com
42+
```
4143

4244
The command will create a CNAME record that points to the Tunnel subdomain, but will not proxy traffic if the Tunnel is not currently running.
4345

0 commit comments

Comments
 (0)