-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
docs: reverse_proxy: Add guide for Caddy #87
Conversation
Thanks for this! And your contribution to Caddy :) I note that your changes don't appear to be in a release yet. It might be worth noting that, or holding off on merging this until they are (but even then it should probably clarify what Caddy version is required). Would love for someone to test this (@turguenev? 🙂 ) and report how they get on. |
Caddy's plugins do not need a release; they are simply based on the $ wget https://github.com/caddyserver/xcaddy/releases/download/v0.2.0/xcaddy_0.2.0_linux_amd64.tar.gz
$ tar -xvzf xcaddy_0.2.0_linux_amd64.tar.gz
$ ./xcaddy build --with github.com/mholt/caddy-l4
$ ./caddy version
v2.4.6 h1:HGkGICFGvyrodcqOOclHKfvJC0qTU7vny/7FhYp9hNw=
$ ./caddy list-modules | grep -E '(xmpp|alpn)'
layer4.matchers.xmpp
tls.handshake_match.alpn
Let me know if you get stuck somewhere; the JSON / YAML syntax takes a bit of getting used to, as opposed to the Caddyfile. |
I will incorporate changes from this discussion on Caddy forums to the PR soon. Hopefully, we should have a testing report to go along. |
Thanks Rijul! |
Closes snikket-im#82 Based on snikket-im#87 and discussion in Caddy forums, consolidate information into basic and advanced configuration. The basic set up is easy to use, and only forward HTTP/S traffic. The advanced set up requires additional plugins, and allows Caddy to be used in place of `sslh` with the added advantage of forwarding port 80 - allowing Snikket to obtain certificates by itself.
Closes snikket-im#82 Based on snikket-im#87 and discussion in Caddy forums, consolidate information into basic and advanced configuration. The basic set up is easy to use, and only forward HTTP/S traffic. The advanced set up requires additional plugins, and allows Caddy to be used in place of `sslh` with the added advantage of forwarding port 80 - allowing Snikket to obtain certificates by itself.
Closes snikket-im#82 Based on snikket-im#87 and discussion in Caddy forums, consolidate information into basic and advanced configuration. The basic set up is easy to use, and only forwards HTTP/S traffic. The advanced set up requires additional plugins, and allows Caddy to be used in place of `sslh` with the added advantage of forwarding port 80 - allowing Snikket to obtain certificates by itself.
Closes snikket-im#82 Based on snikket-im#87 and discussion in Caddy forums, consolidate information into basic and advanced configuration. The basic set up is easy to use, and only forwards HTTP/S traffic. The advanced set up requires additional plugins, and allows Caddy to be used in place of `sslh` with the added advantage of forwarding port 80 - allowing Snikket to obtain certificates by itself. See also mholt/caddy-l4#39
Now that mholt/caddy-l4#33 has been merged, Caddy can be used as a reverse proxy for Snikket with all the features of
sslh
, and forwarding port 80 to Snikket's 5080.