Description
thoughts
💠Coder needs a "Configure" documentation page similar to:
- https://docs.gitlab.com/omnibus/settings/ssl.html
- https://docs.gitlab.com/omnibus/settings/ssl.html#configure-a-reverse-proxy-or-load-balancer-ssl-termination
goals
- a zero-knowledge assumed tutorial (such as done by digital ocean) that provides examples of configuring
CODER_ACCESS_URL
topics
- ensuring DNS records pointing to an accessible IP address (either public, lan or tailnet)
- introduction to letsencrypt and caddy
- example of caddy (thus letsencrypt) + coder that folks can copy/paste to their way to success
scenarios
- simple /r/homelab scenario
- production scenarios that are more complex such as k8 ingress.
considerations
- should docker-compose.yml also include ingress via caddy by default? https://github.com/coder/coder/blob/main/docker-compose.yaml
references
Ensure you have an externally-reachable CODER_ACCESS_URL set in your helm chart. If you do not have a domain set up, this should be the IP address of Coder's LoadBalancer (kubectl get svc -n coder).
Set CODER_ACCESS_URL to the external URL that users and workspaces will use to connect to Coder. This is not required if you are using the tunnel. Learn more about Coder's configuration options.
https://coder.com/docs/coder-oss/latest/install/packages
CODER_ACCESS_URL is required if you are not using the tunnel. Set this to the external URL that users and workspaces use to connect to Coder (e.g. https://coder.example.com/). This should not be localhost.
https://coder.com/docs/coder-oss/latest/admin/configure#access-url