Skip to content

fix: wildcard dns docs #7709

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 2 commits into from
May 31, 2023
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
Clarify
Signed-off-by: Spike Curtis <spike@coder.com>
  • Loading branch information
spikecurtis committed May 30, 2023
commit 4dd1e4cf904de4beea1a584945eec14144278380
9 changes: 5 additions & 4 deletions docs/admin/configure.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,11 +40,12 @@ subdomain that resolves to Coder (e.g. `*.coder.example.com`).

If you are providing TLS certificates directly to the Coder server, either

1. use a single certificate/key for the root and wildcard domains.
2. configure both root and wildcard domain certificates/keys via
1. Use a single certificate and key for both the root and wildcard domains.
2. Configure multiple certificates and keys via
[`coder.tls.secretNames`](https://github.com/coder/coder/blob/main/helm/values.yaml) in the Helm Chart, or
[`--tls-key-file`](../cli/server#--tls-cert-file) and [`--tls-key-file`](../cli/server#--tls-key-file) command
line options.
[`--tls-cert-file`](../cli/server#--tls-cert-file) and [`--tls-key-file`](../cli/server#--tls-key-file) command
line options (these both take a comma separated list of files; list certificates and their respective keys in the
same order).

## TLS & Reverse Proxy

Expand Down