extern/zrok
1
1
Fork 0
mirror of https://github.com/openziti/zrok.git synced 2025-01-03 12:39:07 +01:00
Code Issues Packages Projects Releases Wiki Activity

tweak self-hosting guide

Browse Source
This commit is contained in:
Kenneth Bingham 2023-04-06 13:38:48 -04:00
parent d712d5eeeb
commit db8d2e55a3
No known key found for this signature in database
GPG Key ID: 31709281860130B6
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/guides/self-hosting/self_hosting_guide.md
View File

@ -179,7 +179,9 @@ Nice work! The `zrok` controller is fully configured now that you have created t
## Configure the Public Frontend ## 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. The frontend does not provide server TLS, but you may front the server with a reverse proxy. It is essential the reverse proxy forwards the `Host` header supplied by the viewer. This example will expose the non-TLS listener for the frontend. Create `etc/http-frontend.yml`. This frontend config file has a `host_match` pattern that represents the DNS zone you're using with this instance of zrok. Incoming HTTP requests with a matching `Host` header will be handled by this frontend. You may also specify the interface 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. It is essential the reverse proxy forwards the `Host` header supplied by the viewer. This example will expose the non-TLS listener for the frontend.
```yaml ```yaml
host_match: zrok.quigley.com host_match: zrok.quigley.com