diff --git a/README.md b/README.md index 84a7a2a0..072dbbdf 100644 --- a/README.md +++ b/README.md @@ -36,7 +36,7 @@ See the [Concepts and Getting Started Guide](docs/getting-started.md) for a full The single `zrok` binary contains everything you need to operate `zrok` environments and also host your own service instances. Just add an OpenZiti network and you're up and running. -See the [Self-Hosting Guide](docs/guides/v0.3_self_hosting_guide.md) for details on getting your own `zrok` service instance running. This builds on top of the [OpenZiti Quick Start](https://docs.openziti.io/docs/learn/quickstarts/network/) to have a running `zrok` service instance in minutes. +See the [Self-Hosting Guide](docs/guides/self_hosting_guide.md) for details on getting your own `zrok` service instance running. This builds on top of the [OpenZiti Quick Start](https://docs.openziti.io/docs/learn/quickstarts/network/) to have a running `zrok` service instance in minutes. ## Building diff --git a/docs/core-features/hosting.md b/docs/core-features/hosting.md index 59523345..20e44264 100644 --- a/docs/core-features/hosting.md +++ b/docs/core-features/hosting.md @@ -5,7 +5,7 @@ sidebar_position: 200 ## Self-Hosted -`zrok` is not limited to a managed offering. You can [host your own](../guides/self-hosting/v0.3_self_hosting_guide.md) instance of `zrok` as well. `zrok` is +`zrok` is not limited to a managed offering. You can [host your own](../guides/self-hosting/self_hosting_guide.md) instance of `zrok` as well. `zrok` is also freely available as open source software hosted by GitHub under a very permissive Apache v2 license. ## Managed Service diff --git a/docs/getting-started.md b/docs/getting-started.md index d2d81b50..ff8d83c1 100644 --- a/docs/getting-started.md +++ b/docs/getting-started.md @@ -430,7 +430,7 @@ You use the `zrok reserve` command to create _reserved shares_. Reserved shares ## Self-Hosting a Service Instance -Interested in self-hosting your own `zrok` service instance? See the [self-hosting guide](./guides/self-hosting/v0.3_self_hosting_guide.md) for details. +Interested in self-hosting your own `zrok` service instance? See the [self-hosting guide](./guides/self-hosting/self_hosting_guide.md) for details. [openziti]: https://docs.openziti.io/docs/learn/introduction/ "OpenZiti" [ zrok-download]: https://zrok.io "Zrok Download" diff --git a/docs/guides/metrics-and-limits/configuring-metrics.md b/docs/guides/metrics-and-limits/configuring-metrics.md index 5d58cfc7..b0072f43 100644 --- a/docs/guides/metrics-and-limits/configuring-metrics.md +++ b/docs/guides/metrics-and-limits/configuring-metrics.md @@ -92,12 +92,12 @@ metrics: queue_name: events influx: url: "http://127.0.0.1:8086" - bucket: zrok - org: zrok + bucket: zrok # the bucket and org must be + org: zrok # created in advance in InfluxDB token: "" ``` -This configures the `zrok` controller to consume usage events from the AMQP queue, and configures the InfluxDB metrics store. +This configures the `zrok` controller to consume usage events from the AMQP queue, and configures the InfluxDB metrics store. The InfluxDB organization and bucket must be created in advance. The `zrok` controller will not create these for you. ## Testing Metrics diff --git a/docs/guides/self-hosting/v0.3_nginx_tls_guide.md b/docs/guides/self-hosting/nginx_tls_guide.md similarity index 97% rename from docs/guides/self-hosting/v0.3_nginx_tls_guide.md rename to docs/guides/self-hosting/nginx_tls_guide.md index 438d1164..183a471a 100644 --- a/docs/guides/self-hosting/v0.3_nginx_tls_guide.md +++ b/docs/guides/self-hosting/nginx_tls_guide.md @@ -11,7 +11,7 @@ sidebar_label: Nginx TLS ## Before You Begin -I'll assume you have a running zrok controller and public frontend and wish to front both with Nginx providing server TLS. Go back to [Self-Hosting Guide](./v0.3_self_hosting_guide.md) if you still need to spin those up. +I'll assume you have a running zrok controller and public frontend and wish to front both with Nginx providing server TLS. Go back to [Self-Hosting Guide](./self_hosting_guide.md) if you still need to spin those up. ## Choose a Reverse Proxy Address diff --git a/docs/guides/self-hosting/v0.3_self_hosting_guide.md b/docs/guides/self-hosting/self_hosting_guide.md similarity index 94% rename from docs/guides/self-hosting/v0.3_self_hosting_guide.md rename to docs/guides/self-hosting/self_hosting_guide.md index 54031813..84dec517 100644 --- a/docs/guides/self-hosting/v0.3_self_hosting_guide.md +++ b/docs/guides/self-hosting/self_hosting_guide.md @@ -47,7 +47,7 @@ Create a controller configuration file in `etc/ctrl.yml`. The controller does no # /___|_| \___/|_|\_\ # controller configuration -v: 2 +v: 3 admin: secrets: @@ -179,7 +179,9 @@ Nice work! The `zrok` controller is fully configured now that you have created t ## 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 host_match: zrok.quigley.com