[Teams] Tunnel guides + Gateway tutorial#2114
Conversation
| pcx-content-type: reference | ||
| --- | ||
|
|
||
| # Install `cloudflared` |
There was a problem hiding this comment.
@abelinkinbio @sudarshan-reddy the idea is to make this a download page, and move everything re: installation to its own Tunnel guide, one for each OS. wdyt?
There was a problem hiding this comment.
This is a good idea! I think this page is a bit cluttered and this will help. However, maybe we can do something like a modal for each OS only when the instructions diverge keeping the rest common? (For example, I love what Go does here: https://golang.org/doc/install)
| mv /root/cloudflared/cloudflared /usr/bin/cloudflared | ||
| ``` | ||
|
|
||
| ## 3. Authenticate cloudflared. |
There was a problem hiding this comment.
| ## 3. Authenticate cloudflared. | |
| ## 1. Authenticate cloudflared |
| * Open a browser window and prompt you to log into your Cloudflare account. After logging into your account, select your hostname. | ||
| * Generate a [cert.pem file](/connections/connect-apps/tunnel-useful-terms#cert-pem). The `cert.pem` file contains account-wide credentials. | ||
|
|
||
| ## 4. Create a tunnel and give it a name. |
There was a problem hiding this comment.
| ## 4. Create a tunnel and give it a name. | |
| ## 1. Create a tunnel and give it a name |
|
|
||
| From the output of the command, take note of the tunnel’s UUID and the path to your tunnel’s credentials file. | ||
|
|
||
| ## 5. Create a configuration file. |
There was a problem hiding this comment.
| ## 5. Create a configuration file. | |
| ## 1. Create a configuration file |
| credentials-file: /root/.cloudflared/6ff42ae2-765d-4adf-8112-31c55c1551ef.json | ||
| ``` | ||
|
|
||
| ## 6. Start routing traffic. |
There was a problem hiding this comment.
| ## 6. Start routing traffic. | |
| ## 1. Start routing traffic |
| $ cloudflared tunnel route ip show | ||
| ``` | ||
|
|
||
| ## 7. Run the tunnel. |
There was a problem hiding this comment.
| ## 7. Run the tunnel. | |
| ## 1. Run the tunnel |
|
|
||
| Cloudflare Tunnel can install itself as a system service on Linux and Windows and as a launch agent on macOS. For more information, see [Run as a service](/connections/connect-apps/run-tunnel/run-as-service). | ||
|
|
||
| ## 8. Check the tunnel |
There was a problem hiding this comment.
| ## 8. Check the tunnel | |
| ## 1. Check the tunnel |
There was a problem hiding this comment.
I've just realized something: I'm not sure if changing every H2 to ## 1. will create the correct numbers automatically because you have pieces of code between each H2. If that's the case and you see that upon building your docs the numbered list is wrong, you'll have to add a tab or a couple of spaces (depends on how your VSCode is configured) on the pieces of text between each H2. This will indicate the text is a part of that H2 and number correctly your list
| * Open a browser window and prompt you to log into your Cloudflare account. After logging into your account, select your hostname. | ||
| * Generate a [cert.pem file](/connections/connect-apps/tunnel-useful-terms#cert-pem). The `cert.pem` file contains account-wide credentials. | ||
|
|
||
| ## 3. Create a tunnel and give it a name. |
There was a problem hiding this comment.
| ## 3. Create a tunnel and give it a name. | |
| ## 1. Create a tunnel and give it a name |
|
|
||
| </Aside> | ||
|
|
||
| ## 1. Download `cloudflared`. |
There was a problem hiding this comment.
| ## 1. Download `cloudflared`. | |
| ## 1. Download `cloudflared` |
|
|
||
| </Aside> | ||
|
|
||
| ## 1. Download `cloudflared`. |
There was a problem hiding this comment.
| ## 1. Download `cloudflared`. | |
| ## 1. Download `cloudflared` |
| mv /root/cloudflared/cloudflared /usr/bin/cloudflared | ||
| ``` | ||
|
|
||
| ## 3. Authenticate `cloudflared`. |
There was a problem hiding this comment.
| ## 3. Authenticate `cloudflared`. | |
| ## 1. Authenticate `cloudflared` |
|
|
||
| From the output of the command, take note of the tunnel’s UUID and the path to your tunnel’s credentials file. | ||
|
|
||
| ## 5. Create a configuration file. |
There was a problem hiding this comment.
| ## 5. Create a configuration file. | |
| ## 1. Create a configuration file |
No description provided.