extern/zrok
1
1
Fork 0
mirror of https://github.com/openziti/zrok.git synced 2024-11-28 11:04:04 +01:00
Code Issues Packages Projects Releases Wiki Activity

zrok-private-access

Browse Source
This commit is contained in:
Michael Quigley 2024-07-10 12:49:27 -04:00
parent 93cdbe9aa9
commit 27b605783f
No known key found for this signature in database
GPG Key ID: 9B60314A9DD20A62
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/guides/self-hosting/personalized-frontend.md
View File

@ -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 guide](../../frontdoor/), or [zrok-private-access Docker Compose guide](../../docker-share/docker_private_share_guide/#access-the-private-share) 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