61–70 of 115 posts
Earlier quoted context omitted.
I'm a heavy nginx user - there's not much that I haven't already done with it and I know the documentation quite well. Why would someone like me change to Caddy? I can see there are some NGINX Plus features that are free in Caddy.
Single binary is nice, live config changes, let’s encrypt is built in.
After more than 10 year nginx, I switched to Caddy and never regretted a moment.
Is Caddy scriptable? I don't know much about it. But ever since I discovered nginx-lua-module and OpenResty it's been pretty much a game-changer for me. Curious if other popular webservers have done similar? Not really talking about things like mod_perl/php. Although I guess those are somewhat the same thing.
It's also very easy to write plugins for Caddy: https://caddyserver.com/docs/extending-caddy
I utterly adore your project. Thank you so much. Are there plans for SMTP or IMAP proxying? Do you do SNI proxying too? I would love for Caddy to be my one stop shop for all TLS termination.
"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."
But Caddy's http server can also do basic logic around SNI if I recall correctly.
Does anyone use caddy in production? At what loads?
After more than 10 year nginx, I switched to Caddy and never regretted a moment.
If tailscale doesn't provide it, anyone know of a DNS server that's caddy-like in simplicity and dead simple ease of running on localhost with minimal config, secure by default, etc?
Wow the new features sound great. Does tailscale run a local DNS server or provide AAAA or SRV records that the new dynamic upstream could connect to directly? The combo of dynamic upstream and dynamic HTTPS certs automatically from tailscale would be really nice. I'd love to just run tailscale and caddy locally on all machines and instantly have 100% proper browser HTTPS and DNS name access to all my tailscale servi…
Basically this is more about grabbing the TLS cert from Tailscale's daemon. How you handle the request is up to you. It's not related to the dynamic upstreams feature.
I use distributions because I care about security and I'll be downvoted to oblivion for saying this.
I'd rather use something that can be packaged and maintained properly by distributions: https://repology.org/project/caddy/versions I use distributions because I care about security and I'll be downvoted to oblivion for saying this.
P.S., from the guidelines:
> Please don't comment about the voting on comments. It never does any good, and it makes boring reading.
edit: and an official response https://news.ycombinator.com/item?id=31170881