Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add funnel support #26

Open
AstraLuma opened this issue Dec 21, 2023 · 1 comment
Open

Add funnel support #26

AstraLuma opened this issue Dec 21, 2023 · 1 comment

Comments

@AstraLuma
Copy link

Allow the use of funnel to be specified per-binding in the Caddyfile.

@kernelb00t
Copy link

Yes, this is very useful, consider this use case:

  • Multiple Docker services (Vaultwarden, portainer and docuseal for example)
  • A Caddy server running as a Systemd service

How can you get vaultwarden AND docuseal to the web, without opening ports? With the default limitations with the tailscale CLI, you will have only 3 ports available, and your address name will look like server1.net-work.ts.net:8080. This does not look professional to people who don't knows Tailscale, and will be reticent to click on the link. For Bitwarden this is less an issue, because that's your passwords and not others, but for DocuSeal, people will just think this guy want to send me a malware. This would allow more stability and containerize more of the parts of software that touches Internet, to limit threats in case of an hypothetical breach in Tailscale's CLI and daemon, even if very unlikely.

This is also very practical, to allow versioning of configs (not as simple as removing/re-adding funnel and serve configs).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants