-
Notifications
You must be signed in to change notification settings - Fork 887
docs: add nginx reverse-proxy example #6185
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
Conversation
This PR adds nginx reverse-proxy example to provision coder with tls certificate using letsencrypt certbot. This will partially resolve #6086.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution! I haven't tested it yet, but have some grammar/formatting feedback. We don't have a documented style guide yet, but just some change requests to make the doc read more like the rest of ours.
I can test the wildcard stuff later.
Co-authored-by: Ben Potter <me@bpmct.net>
Co-authored-by: Ben Potter <me@bpmct.net>
Co-authored-by: Ben Potter <me@bpmct.net>
Co-authored-by: Ben Potter <me@bpmct.net>
Co-authored-by: Ben Potter <me@bpmct.net>
Co-authored-by: Ben Potter <me@bpmct.net>
Co-authored-by: Ben Potter <me@bpmct.net>
Co-authored-by: Ben Potter <me@bpmct.net>
Co-authored-by: Ben Potter <me@bpmct.net>
Co-authored-by: Ben Potter <me@bpmct.net>
Co-authored-by: Ben Potter <me@bpmct.net>
Co-authored-by: Ben Potter <me@bpmct.net>
Co-authored-by: Ben Potter <me@bpmct.net>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another cycle of reviews. I'll probably look one more time while I test it out (beware: I may have even more formatting suggestions lol)
Co-authored-by: Ben Potter <me@bpmct.net>
Co-authored-by: Ben Potter <me@bpmct.net>
updated with most of your suggestions. |
Hello, can I suggest using the |
Thank you for your suggestion. This is a WIP, and I still need to test this with a wildcard domain. I will update. |
@bpmct I have tested this, and it works. You may review it and merge it after testing. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
examples/web-server/nginx/README.md
Outdated
|
||
## Requirements | ||
|
||
1. Start a Coder deployment with a wildcard subdomain. See [this guide](https://coder.com/docs/v2/latest/admin/configure#wildcard-access-url) for more information. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I noticed it was important to have HTTP_ADDRESS as 3000. Plus the access URL is also important to set.
1. Start a Coder deployment with a wildcard subdomain. See [this guide](https://coder.com/docs/v2/latest/admin/configure#wildcard-access-url) for more information. | |
1. Start a Coder deployment and be sure to set the following [configuration values](https://coder.com/docs/v2/latest/admin/configure): | |
```console | |
CODER_HTTP_ADDRESS=127.0.0.1:3000 | |
CODER_ACCESS_URL=https://coder.example.com | |
CODER_WILDCARD_ACCESS_URL=*coder.example.com | |
``` | |
Throughout the guide, be sure to replace `coder.example.com` with the domain you intend to use with Coder. |
What do you think about replacing all cases with CODER_SUBDOMAIN
with coder.example.com? We tend to do this in other places in our docs, such as in the Caddy docs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that is a better option. I will replace all YOUR_SUBDOMAIN
with CODER_SUBDOMAIN
Co-authored-by: Ben Potter <me@bpmct.net>
Co-authored-by: Ben Potter <me@bpmct.net>
Co-authored-by: Ben Potter <me@bpmct.net>
This PR adds an Nginx reverse-proxy example to deploy Coder with a wildcard tls certificate using LetsEncrypt Certbot.
This will resolve #6086, along with #6213.
cc: @bpmct
Tested with a wildcard subdomain.