mention server TLS

This may help the next self-hoster. I spent an embarrassing amount of time figuring out how to configure controller server TLS before I found the config struct that confirmed there are no server cert properties in the controller config.
This commit is contained in:
Ken Bingham 2023-01-19 11:46:08 -05:00 committed by GitHub
parent 72013a7da9
commit ff1ba596fc
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -21,7 +21,7 @@ You'll need that generated password (`XO0xHp75uuyeireO2xmmVlK91T7B9fpD`) when bu
## Configure the Controller
Create a controller configuration file in `etc/ctrl.yml`.
Create a controller configuration file in `etc/ctrl.yml`. The controller does not provide server TLS, but you may front the server with a reverse proxy. This example will expose the non-TLS listener for the controller.
```yaml
# _____ __ ___ | | __
@ -144,7 +144,7 @@ Now our `zrok` controller is fully configured.
## Configure the Public Frontend
Create `etc/http-frontend.yml`. You must reiterate the pattern you expressed in the public frontend URL template as a `host_match` pattern, and you may change the default address where the frontend will listen for public access requests.
Create `etc/http-frontend.yml`. You must reiterate the pattern you expressed in the public frontend URL template as a `host_match` pattern, and you may change the default address where the frontend will listen for public access requests. The frontend does not provide server TLS, but you may front the server with a reverse proxy. This example will expose the non-TLS listener for the frontend.
```yaml
host_match: zrok.quigley.com