acmez
caddy-l4
Our great sponsors
acmez | caddy-l4 | |
---|---|---|
4 | 20 | |
248 | 765 | |
- | - | |
6.7 | 7.2 | |
4 days ago | 6 days ago | |
Go | Go | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
acmez
-
Autostrada: A codebase generator for new Go projects
CertMagic uses https://github.com/mholt/acmez because lego has significant problems that made it inflexible and unreliable for use in Caddy. See the History section on that repo for an explanation.
-
Show HN: Caddy v2.5.0
Because Lego maintainers wouldn't budge when Caddy needed changes made to increase ACME reliability. Matt wrote his own implementation https://github.com/mholt/acmez and started using that in Caddy soon after. There's a deeper explanation here: https://github.com/caddyserver/certmagic/issues/71
-
Any "simple" projects with particularly well-written and/or well-documented code for a beginner to look through?
I am really proud of how elegant and well-documented ACMEz is: https://github.com/mholt/acmez
- acmez 1.0: Premier ACME client library for Go
caddy-l4
-
Caddylike solution for SSH/SFTP
https://github.com/mholt/caddy-l4 and https://github.com/kadeessh/kadeessh can do SSH forwarding.
-
Minecraft server with VPS as a proxy
3) Use a L4 TCP/UDP plugin for caddy. https://github.com/mholt/caddy-l4
-
Nginx Reverse Proxy game hosting
Wireguard gives my service servers their own internal IP for the gateway to reference (nothing fancy done with it, no iptables modifications like you may see on other guides), and I use NGINX for the game server proxying, specifically linuxserver's nginx container. I love Caddy, but even with caddy-l4 I couldn't get it working right for Valheim (and thus UDP), but NGINX worked real quick.
- Help routing packets from a static public ip to tailscale device
-
Accessing an IP camera stream through caddy
This may help: https://github.com/mholt/caddy-l4
-
The Future of Nginx: Getting Back to Our Open Source Roots
Well, that's a bit off-topic from the parent comment, which was more about the Caddyfile supporting complex config (versus the underlying JSON config) and not really "complex usecases".
But that said, from a quick Google search... was this an RTMP stream? If so, I suppose you'd want to use https://github.com/mholt/caddy-l4 which is a plugin for Caddy that lets you do TCP-layer things. Caddy's standard distribution just ships an HTTP server (plus TLS and PKI, etc), which is layer-7
You might be able to use caddy-l4's "tee" handler to pipe into multiple "proxy" handlers. But I'm not sure anyone's tried this yet, I had no idea people did this sort of thing. I'd be interested to hear if it does work though.
-
Brand new to this, have a few questions about DDNS, reverse proxies, etc
If you are only having your services accessible via LAN, HTTPS isn't totally necessary, but I would still recommend it. I think a reverse proxy will be easier than your described method. Just set it to listen to 443 and have all of your other services on random ports being proxied from the reverse proxy. If you want HTTPS from your reverse proxy to your services, most reverse proxies will have this kind of feature. Here is the caddy L4 raw TCP stream module: https://github.com/mholt/caddy-l4
-
Alternative to SRV record?
I had a similar problem a while back and found this project (Caddy-L4). It had no releases or examples on how to build it so I forked it and added some Docker stuff.
-
Show HN: Caddy v2.5.0
"Caddy L4" aka "Project Conncept" might be what you're looking for:
https://github.com/mholt/caddy-l4
"Project Conncept is an experimental layer 4 app for Caddy. It facilitates composable handling of raw TCP/UDP connections based on properties of the connection or the beginning of the stream."
-
I'm Using SNI Proxying and IPv6 to Share Port 443 Between Webapps
Nice, this is kind of why I made Project Conncept. It's a powerful TCP and UDP stream multiplexer based on Caddy: https://github.com/mholt/caddy-l4
You can route raw TCP connections by using higher layer protocol matching logic like HTTP properties, SSH, TLS ClientHello info, and more, in composable routes that let you do nearly anything.
What are some alternatives?
boulder - An ACME-based certificate authority, written in Go.
gateway-api - Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.
caddy-json-schema - JSON schema generator for Caddy v2
authelia - The Single Sign-On Multi-Factor portal for web apps
lorelai - ✍ Generate Lorem Ipsum like a pro
ingress - WIP Caddy 2 ingress controller for Kubernetes
chigo - 🌈 Lolcat in Go: Rainbows and Unicorns!
nginx-proxy - Automated nginx proxy for Docker containers using docker-gen
certmagic - Automatic HTTPS for any Go program: fully-managed TLS certificate issuance and renewal
caddy-docker-proxy - Caddy as a reverse proxy for Docker
beep - A little package that brings sound to any Go application. Suitable for playback and audio-processing.
caddy-ssh - Caddy-SSH is a general-purpose, extensible, modular, memory-safe SSH server built in Go [Moved to: https://github.com/kadeessh/kadeessh]