mirror of
https://github.com/coder/coder.git
synced 2026-09-24 15:04:27 +08:00
docs: convert alerts to use GitHub Flavored Markdown (GFM) (#16850)
followup to #16761 thanks @lucasmelin ! + thanks: @ethanndickson @Parkreiner @matifali @aqandrew - [x] update snippet - [x] find/replace - [x] spot-check [preview](https://coder.com/docs/@16761-gfm-callouts/admin/templates/managing-templates/schedule) (and others) --------- Co-authored-by: EdwardAngert <17991901+EdwardAngert@users.noreply.github.com> Co-authored-by: M Atif Ali <atif@coder.com>
This commit is contained in:
co-authored by
EdwardAngert
M Atif Ali
parent
e817713dc0
commit
101b62dc3e
@@ -18,7 +18,8 @@ networking logic.
|
||||
|
||||
In order for clients and workspaces to be able to connect:
|
||||
|
||||
> **Note:** We strongly recommend that clients connect to Coder and their
|
||||
> [!NOTE]
|
||||
> We strongly recommend that clients connect to Coder and their
|
||||
> workspaces over a good quality, broadband network connection. The following
|
||||
> are minimum requirements:
|
||||
>
|
||||
@@ -33,7 +34,8 @@ In order for clients and workspaces to be able to connect:
|
||||
|
||||
In order for clients to be able to establish direct connections:
|
||||
|
||||
> **Note:** Direct connections via the web browser are not supported. To improve
|
||||
> [!NOTE]
|
||||
> Direct connections via the web browser are not supported. To improve
|
||||
> latency for browser-based applications running inside Coder workspaces in
|
||||
> regions far from the Coder control plane, consider deploying one or more
|
||||
> [workspace proxies](./workspace-proxies.md).
|
||||
@@ -172,12 +174,9 @@ more.
|
||||
|
||||
## Browser-only connections
|
||||
|
||||
<blockquote class="info">
|
||||
|
||||
Browser-only connections is an Enterprise and Premium feature.
|
||||
[Learn more](https://coder.com/pricing#compare-plans).
|
||||
|
||||
</blockquote>
|
||||
> [!NOTE]
|
||||
> Browser-only connections is an Enterprise and Premium feature.
|
||||
> [Learn more](https://coder.com/pricing#compare-plans).
|
||||
|
||||
Some Coder deployments require that all access is through the browser to comply
|
||||
with security policies. In these cases, pass the `--browser-only` flag to
|
||||
@@ -189,12 +188,9 @@ via the web terminal and
|
||||
|
||||
### Workspace Proxies
|
||||
|
||||
<blockquote class="info">
|
||||
|
||||
Workspace proxies are an Enterprise and Premium feature.
|
||||
[Learn more](https://coder.com/pricing#compare-plans).
|
||||
|
||||
</blockquote>
|
||||
> [!NOTE]
|
||||
> Workspace proxies are an Enterprise and Premium feature.
|
||||
> [Learn more](https://coder.com/pricing#compare-plans).
|
||||
|
||||
Workspace proxies are a Coder Enterprise feature that allows you to provide
|
||||
low-latency browser experiences for geo-distributed teams.
|
||||
|
||||
@@ -48,17 +48,17 @@ For more examples, see `coder port-forward --help`.
|
||||
|
||||
## Dashboard
|
||||
|
||||
> To enable port forwarding via the dashboard, Coder must be configured with a
|
||||
> [wildcard access URL](../../admin/setup/index.md#wildcard-access-url). If an
|
||||
> access URL is not specified, Coder will create
|
||||
> [a publicly accessible URL](../../admin/setup/index.md#tunnel) to reverse
|
||||
> proxy the deployment, and port forwarding will work.
|
||||
>
|
||||
> There is a
|
||||
> [DNS limitation](https://datatracker.ietf.org/doc/html/rfc1035#section-2.3.1)
|
||||
> where each segment of hostnames must not exceed 63 characters. If your app
|
||||
> name, agent name, workspace name and username exceed 63 characters in the
|
||||
> hostname, port forwarding via the dashboard will not work.
|
||||
To enable port forwarding via the dashboard, Coder must be configured with a
|
||||
[wildcard access URL](../../admin/setup/index.md#wildcard-access-url). If an
|
||||
access URL is not specified, Coder will create
|
||||
[a publicly accessible URL](../../admin/setup/index.md#tunnel) to reverse
|
||||
proxy the deployment, and port forwarding will work.
|
||||
|
||||
There is a
|
||||
[DNS limitation](https://datatracker.ietf.org/doc/html/rfc1035#section-2.3.1)
|
||||
where each segment of hostnames must not exceed 63 characters. If your app
|
||||
name, agent name, workspace name and username exceed 63 characters in the
|
||||
hostname, port forwarding via the dashboard will not work.
|
||||
|
||||
### From an coder_app resource
|
||||
|
||||
@@ -131,12 +131,9 @@ to the app.
|
||||
|
||||
### Configure maximum port sharing level
|
||||
|
||||
<blockquote class="info">
|
||||
|
||||
Configuring port sharing level is an Enterprise and Premium feature.
|
||||
[Learn more](https://coder.com/pricing#compare-plans).
|
||||
|
||||
</blockquote>
|
||||
> [!NOTE]
|
||||
> Configuring port sharing level is an Enterprise and Premium feature.
|
||||
> [Learn more](https://coder.com/pricing#compare-plans).
|
||||
|
||||
Premium-licensed template admins can control the maximum port sharing level for
|
||||
workspaces under a given template in the template settings. By default, the
|
||||
@@ -179,12 +176,14 @@ must include credentials (set `credentials: "include"` if using `fetch`) or the
|
||||
requests cannot be authenticated and you will see an error resembling the
|
||||
following:
|
||||
|
||||
> Access to fetch at
|
||||
> '<https://coder.example.com/api/v2/applications/auth-redirect>' from origin
|
||||
> '<https://8000--dev--user--apps.coder.example.com>' has been blocked by CORS
|
||||
> policy: No 'Access-Control-Allow-Origin' header is present on the requested
|
||||
> resource. If an opaque response serves your needs, set the request's mode to
|
||||
> 'no-cors' to fetch the resource with CORS disabled.
|
||||
```text
|
||||
Access to fetch at
|
||||
'<https://coder.example.com/api/v2/applications/auth-redirect>' from origin
|
||||
'<https://8000--dev--user--apps.coder.example.com>' has been blocked by CORS
|
||||
policy: No 'Access-Control-Allow-Origin' header is present on the requested
|
||||
resource. If an opaque response serves your needs, set the request's mode to
|
||||
'no-cors' to fetch the resource with CORS disabled.
|
||||
```
|
||||
|
||||
#### Headers
|
||||
|
||||
|
||||
@@ -1,13 +1,13 @@
|
||||
# STUN and NAT
|
||||
|
||||
> [Session Traversal Utilities for NAT (STUN)](https://www.rfc-editor.org/rfc/rfc8489.html)
|
||||
> is a protocol used to assist applications in establishing peer-to-peer
|
||||
> communications across Network Address Translations (NATs) or firewalls.
|
||||
>
|
||||
> [Network Address Translation (NAT)](https://en.wikipedia.org/wiki/Network_address_translation)
|
||||
> is commonly used in private networks to allow multiple devices to share a
|
||||
> single public IP address. The vast majority of home and corporate internet
|
||||
> connections use at least one level of NAT.
|
||||
[Session Traversal Utilities for NAT (STUN)](https://www.rfc-editor.org/rfc/rfc8489.html)
|
||||
is a protocol used to assist applications in establishing peer-to-peer
|
||||
communications across Network Address Translations (NATs) or firewalls.
|
||||
|
||||
[Network Address Translation (NAT)](https://en.wikipedia.org/wiki/Network_address_translation)
|
||||
is commonly used in private networks to allow multiple devices to share a
|
||||
single public IP address. The vast majority of home and corporate internet
|
||||
connections use at least one level of NAT.
|
||||
|
||||
## Overview
|
||||
|
||||
@@ -33,8 +33,9 @@ counterpart can be reached. Once communication succeeds in one direction, we can
|
||||
inspect the source address of the received packet to determine the return
|
||||
address.
|
||||
|
||||
> The below glosses over a lot of the complexity of traversing NATs. For a more
|
||||
> in-depth technical explanation, see
|
||||
> [!TIP]
|
||||
> The below glosses over a lot of the complexity of traversing NATs.
|
||||
> For a more in-depth technical explanation, see
|
||||
> [How NAT traversal works (tailscale.com)](https://tailscale.com/blog/how-nat-traversal-works).
|
||||
|
||||
At a high level, STUN works like this:
|
||||
|
||||
@@ -104,10 +104,10 @@ CODER_TLS_KEY_FILE="<key_file_location>"
|
||||
|
||||
### Running on Kubernetes
|
||||
|
||||
Make a `values-wsproxy.yaml` with the workspace proxy configuration:
|
||||
Make a `values-wsproxy.yaml` with the workspace proxy configuration.
|
||||
|
||||
> Notice the `workspaceProxy` configuration which is `false` by default in the
|
||||
> coder Helm chart.
|
||||
Notice the `workspaceProxy` configuration which is `false` by default in the
|
||||
Coder Helm chart:
|
||||
|
||||
```yaml
|
||||
coder:
|
||||
|
||||
Reference in New Issue
Block a user