Skip to content

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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Nov 9, 2022
Merged
Changes from 1 commit
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
Prev Previous commit
Next Next commit
resolve another linting issue
  • Loading branch information
ghuntley committed Nov 9, 2022
commit 2a809d13a19018473cd855450a6088d5e525a367
4 changes: 2 additions & 2 deletions docs/secrets.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

<blockquote class="info">
This article explains how to use secrets in a workspace. To authenticate the
workspace provisioner, see <a href="./templates/authentication">this</a>.
workspace provisioner, see [this](./admin/auth).
</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

<a href="./templates#parameters">Template parameters</a> are a dangerous way to accept secrets.
[Template parameters](./templates#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