Skip to content

Commit 77f7525

Browse files
authored
Update README.md
1 parent 40b8be5 commit 77f7525

File tree

1 file changed

+7
-8
lines changed

1 file changed

+7
-8
lines changed

README.md

+7-8
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,8 @@
1-
# Self-hosted Gateway
1+
## A new version is under development
2+
Interested in getting involved with world changing open source software?
3+
Check out the next (WIP) iteration of this project: https://github.com/fractalnetworksco/fractal-link
4+
5+
## Self-hosted Gateway
26
**Jump to [Getting Started](#getting-started)**
37
## Features and Benefits
48
- Docker native self-hosted alternative to Cloudflare Tunnels, Tailscale Funnel, ngrok and others.
@@ -205,20 +209,15 @@ services:
205209
$ docker ps
206210
```
207211
208-
### Limitations
209-
210-
- Currently only IPv4 is supported
211-
- Raw UDP proxying is supported but is currently untested & undocumented, see bottom of `gateway/link-entrypoint.sh`.
212-
213212
### FAQ
214213
215214
- How is this better than setting up nginx and WireGuard myself on a VPS?
216215
217-
The goal of this project is to self-hosting more accessible and reproducible. This selfhosted-gateway leverages a "ZeroTrust" network architecture (see diagram above). Each "Link" provides a dedicated WireGuard tunnel that is isolated from other containers and the underlying. This isolation is provided by Docker Compose's creation of a private Docker network for each compose file (project).
216+
The goal of this project is to make self-hosting more accessible and reproducible. This project leverages a "ZeroTrust" network architecture. Each "Link" provides a dedicated WireGuard tunnel that is isolated from other containers and the underlying host. This isolation is provided by Docker Compose's creation of a private Docker network for each compose project.
218217
219218
- Can I still access the service from my local network?
220219
221-
You will need to expose ports in your Docker host as you would traditionally, but this is no longer necessary:
220+
Yes, just expose ports in your Docker host as you would normally:
222221
```
223222
ports:
224223
- 80:80

0 commit comments

Comments
 (0)