selfhosted-gateway
selfhosted-gateway copied to clipboard
Self-hosted Docker native tunneling to localhost. Expose local docker containers to the public Internet via a simple docker compose interface.
This allows users to create link containers for containerized services that require ports other than the typical 80/443 ports for HTTP/HTTPS. I have tested this with a Minecraft container for...
previously *.app.domain.com was routed to a single link, a contributor submitted an enhancement to disambiguate sub.sub domains making the default behavior as routing different sub.subdomain.domain domains to different links (requiring...
Currently, create_link.sh launches a standalone container on the gateway for each link, instead lets write links to the same docker compose so the gateway operator can easily modify links without...
Current behavior of `make link ...` is to output a docker-compose service snippet with WireGuard parameters as environment variables. A welcome convenience would be the ability to output a WireGuard...
My VPS appeared to crashed, all my link containers stayed up but lost connection. I'm able to create links fine which create the containers correctly and have set this up...
Hi, I have an existing NPM container running on my home server. Is it possible to point the traffic from the VPS to the NPM? For example: VPS (immich.domain.com) >...
Running throught the instructions it appears that its possible to essentially tunnel all traffic for a single subdomain to a "backend" reverse proxy to handle the TLS/SSL encryption and forwarding...
When creating a link at the gateway we use the FQDN to resolve the Gateway IP. We should use the resolved IP for determining where to create links instead of...
add documentation for mTLS client authentication with Caddy. This needs Caddy >=2.8.