You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Relocate Apache, Caddy, and NGINX configuration from examples.
- Update internal links for configuration guides to reflect new paths.
- Improve documentation structure by centralizing setup resources.
1. Modify the [Caddyfile](./Caddyfile) and change the following values:
25
25
26
26
-`localhost:3000`: Change to `coder:7080` (Coder container on Docker network)
27
27
-`email@example.com`: Email to request certificates from LetsEncrypt/ZeroSSL (does not have to be Coder admin email)
28
28
-`coder.example.com`: Domain name you're using for Coder.
29
-
-`*.coder.example.com`: Domain name for wildcard apps, commonly used for [dashboard port forwarding](https://coder.com/docs/networking/port-forwarding#dashboard). This is optional and can be removed.
29
+
-`*.coder.example.com`: Domain name for wildcard apps, commonly used for [dashboard port forwarding](../../../networking/port-forwarding.md). This is optional and can be removed.
30
30
31
31
1. Start Coder. Set `CODER_ACCESS_URL` and `CODER_WILDCARD_ACCESS_URL` to the domain you're using in your Caddyfile.
32
32
@@ -38,7 +38,7 @@ This is an example configuration of how to use Coder with [caddy](https://caddys
38
38
39
39
### Standalone
40
40
41
-
1. If you haven't already, [install Coder](https://coder.com/docs/install)
41
+
1. If you haven't already, [install Coder](../../../../install/README.md)
@@ -48,11 +48,11 @@ This is an example configuration of how to use Coder with [caddy](https://caddys
48
48
49
49
-`email@example.com`: Email to request certificates from LetsEncrypt/ZeroSSL (does not have to be Coder admin email)
50
50
-`coder.example.com`: Domain name you're using for Coder.
51
-
-`*.coder.example.com`: Domain name for wildcard apps, commonly used for [dashboard port forwarding](https://coder.com/docs/networking/port-forwarding#dashboard). This is optional and can be removed.
51
+
-`*.coder.example.com`: Domain name for wildcard apps, commonly used for [dashboard port forwarding](../../../networking/port-forwarding.md). This is optional and can be removed.
52
52
-`localhost:3000`: Address Coder is running on. Modify this if you changed `CODER_HTTP_ADDRESS` in the Coder configuration.
53
53
-_DO NOT CHANGE the `ask http://example.com` line! Doing so will result in your certs potentially not being generated._
54
54
55
-
4.[Configure Coder](https://coder.com/docs/admin/configure) and change the following values:
55
+
4.[Configure Coder](../../README.md) and change the following values:
@@ -95,7 +95,7 @@ This is an example configuration of how to use Coder with [caddy](https://caddys
95
95
96
96
## Generating wildcard certificates
97
97
98
-
By default, this configuration uses Caddy's [on-demand TLS](https://caddyserver.com/docs/caddyfile/options#on-demand-tls) to generate a certificate for each subdomain (e.g. `app1.coder.example.com`, `app2.coder.example.com`). When users visit new subdomains, such as accessing [ports on a workspace](../../../docs/networking/port-forwarding.md), the request will take an additional 5-30 seconds since a new certificate is being generated.
98
+
By default, this configuration uses Caddy's [on-demand TLS](https://caddyserver.com/docs/caddyfile/options#on-demand-tls) to generate a certificate for each subdomain (e.g. `app1.coder.example.com`, `app2.coder.example.com`). When users visit new subdomains, such as accessing [ports on a workspace](../../../networking/port-forwarding.md), the request will take an additional 5-30 seconds since a new certificate is being generated.
99
99
100
100
For production deployments, we recommend configuring Caddy to generate a wildcard certificate, which requires an explicit DNS challenge and additional Caddy modules.
0 commit comments