From ab3a376128e176a1d77e36d6bdea535a322e2c6a Mon Sep 17 00:00:00 2001 From: Emil Sandnabba Date: Wed, 14 Aug 2024 23:37:11 +0200 Subject: [PATCH] Update docs/docs/guides/reverse_proxy.md Co-authored-by: Josh Hawkins <32435876+hawkeye217@users.noreply.github.com> --- docs/docs/guides/reverse_proxy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/guides/reverse_proxy.md b/docs/docs/guides/reverse_proxy.md index 001ca4609..c7bef6bf9 100644 --- a/docs/docs/guides/reverse_proxy.md +++ b/docs/docs/guides/reverse_proxy.md @@ -5,7 +5,7 @@ title: Setting up a reverse proxy This guide outlines the basic configuration steps needed to set up a reverse proxy in front of your Frigate instance. -A reverse proxy is typically needed if you want to set up Frigate on a custom URL, on a subdomain or on a host serving multiple sites. It could also be used to set up your own authentication provider or for more advanced HTTP routing. +A reverse proxy is typically needed if you want to set up Frigate on a custom URL, on a subdomain, or on a host serving multiple sites. It could also be used to set up your own authentication provider or for more advanced HTTP routing. Before setting up a reverse proxy, check if any of the built-in functionality in Frigate suits your needs: |Topic|Docs|