You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7-8
Original file line number
Diff line number
Diff 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
2
6
**Jump to [Getting Started](#getting-started)**
3
7
## Features and Benefits
4
8
- Docker native self-hosted alternative to Cloudflare Tunnels, Tailscale Funnel, ngrok and others.
@@ -205,20 +209,15 @@ services:
205
209
$ docker ps
206
210
```
207
211
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
-
213
212
### FAQ
214
213
215
214
- How is this better than setting up nginx and WireGuard myself on a VPS?
216
215
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.
218
217
219
218
- Can I still access the service from my local network?
220
219
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:
0 commit comments