Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

docs: update port forwarding to state it works without a wildcard with tunnel#4887

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
ghuntley merged 7 commits intomainfromdocs-port-forwarding-tunnel
Nov 9, 2022
Merged
Show file tree
Hide file tree
Changes fromall commits
Commits
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletiondocs/networking/port-forwarding.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -45,7 +45,11 @@ 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/configure.md#wildcard-access-url).
>[wildcard access URL](../admin/configure.md#wildcard-access-url). If an access
>URL is not specified, Coder will create[a publicly accessible URL](../admin/configure.md#tunnel)
>to reverse proxy the deployment, and port forwarding will work. There is a
>known limitation where if the port forwarding URL length is greater than 63
>characters, port forwarding will not work.
###From an arbitrary port

Expand Down
4 changes: 2 additions & 2 deletionsdocs/secrets.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -2,7 +2,7 @@

<blockquoteclass="info">
This article explains how to use secrets in a workspace. To authenticate the
workspace provisioner, see<ahref="./templates/authentication">this</a>.
workspace provisioner, see[this](./admin/auth.md).
</blockquote>

Coder is open-minded about how you get your secrets into your workspaces.
Expand All@@ -20,7 +20,7 @@ Often, this workflow is simply:
1. Your users write them to a persistent file after
they've built their workspace

<ahref="./templates#parameters">Template parameters</a> are a dangerous way to accept secrets.
[Template parameters](./templates.md#parameters)> are a dangerous way to accept secrets.
We show parameters in cleartext around the product. Assume anyone with view
access to a workspace can also see its parameters.

Expand Down
[8]ページ先頭
©2009-2025 Movatter.jp