From 93cdbe9aa93e2dfbbd639d89385a853d07ec33f9 Mon Sep 17 00:00:00 2001 From: Michael Quigley Date: Tue, 9 Jul 2024 14:14:45 -0400 Subject: [PATCH] link, again --- docs/guides/self-hosting/personalized-frontend.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/self-hosting/personalized-frontend.md b/docs/guides/self-hosting/personalized-frontend.md index a92e6ae5..548faa12 100644 --- a/docs/guides/self-hosting/personalized-frontend.md +++ b/docs/guides/self-hosting/personalized-frontend.md @@ -34,7 +34,7 @@ Imagine that we own the domain `example.com`. In our example, we want to expose We can accomplish this easily with cheap VPS instance. You could also do it with containers through a container hosting service. The VPS will need an IP address exposed to the internet. You'll also need to be able to create DNS entries for the `example.com` domain. -To accomplish this, we're going to run 3 separate `zrok access private` commands on our VPS (see the [frontdoor](../frontdoor/) guide for details on an approach for setting this up). One command each for shares `A`, `B`, and `C`. The `zrok access private` command works like this: +To accomplish this, we're going to run 3 separate `zrok access private` commands on our VPS (see the [frontdoor](../../frontdoor/) guide for details on an approach for setting this up). One command each for shares `A`, `B`, and `C`. The `zrok access private` command works like this: ``` $ zrok access private