Uhh, I'm almost embarrassed that I had never even heard of Caddy.... Reading about it, good grief it looks amazing. Any experienced users here have any comments on Caddy vs traditional http[s]...
Uhh, I'm almost embarrassed that I had never even heard of Caddy....
Reading about it, good grief it looks amazing.
Any experienced users here have any comments on Caddy vs traditional http[s] servers [apache, nginx etc]?
I've used it successfully in production. I love it, wouldn't go back to nginx unless I was dealing with extremely performance critical paths. My main issue with selling it as a tech has always...
I've used it successfully in production. I love it, wouldn't go back to nginx unless I was dealing with extremely performance critical paths.
My main issue with selling it as a tech has always been the weird license.
Shout if you need help :) Caddy has a lot of neat features. They don't necessarily make sense in production but can be super useful for hobbyist websites. I recommend going through the docs,...
Shout if you need help :)
Caddy has a lot of neat features. They don't necessarily make sense in production but can be super useful for hobbyist websites. I recommend going through the docs, specifically the Caddyfile reference, to see how much it can do.
Take a look at Traefik as well - it and Caddy are quite similar, both in terms of being written in Go, as well as feature set (things like builtin Let's Encrypt support)
Take a look at Traefik as well - it and Caddy are quite similar, both in terms of being written in Go, as well as feature set (things like builtin Let's Encrypt support)
Thanks very much for that recommendation. It also looks like something I'll use heavily. Yeah, it's things like this which give me a good kick up the butt and make me ask myself why I'm still...
Thanks very much for that recommendation. It also looks like something I'll use heavily.
Yeah, it's things like this which give me a good kick up the butt and make me ask myself why I'm still messing around with apache proxypass, lol.
I've never used it in production in a serious way, but currently everything that I self-host is fronted by caddy. I love it; as @Adys mentioned, it has some great features for hobbyists! The built...
I've never used it in production in a serious way, but currently everything that I self-host is fronted by caddy. I love it; as @Adys mentioned, it has some great features for hobbyists! The built in, no-config Let's Encrypt/HTTPS support is also an absolute god-send.
Things like the file manager and markdown rendering are super cool, even though I've not used them. FWIW I set it up in production here and it still runs the HSReplay.net servers to my knowledge...
Things like the file manager and markdown rendering are super cool, even though I've not used them.
FWIW I set it up in production here and it still runs the HSReplay.net servers to my knowledge (Stack goes something like Cloudflare => AWS ECS => Docker => Caddy => uwsgi => Django).
Uhh, I'm almost embarrassed that I had never even heard of Caddy....
Reading about it, good grief it looks amazing.
Any experienced users here have any comments on Caddy vs traditional http[s] servers [apache, nginx etc]?
I've used it successfully in production. I love it, wouldn't go back to nginx unless I was dealing with extremely performance critical paths.
My main issue with selling it as a tech has always been the weird license.
Thanks, I think I'm going to give it a test run this weekend, and then test out the feasibility of replacing some of my own sites with this.
Shout if you need help :)
Caddy has a lot of neat features. They don't necessarily make sense in production but can be super useful for hobbyist websites. I recommend going through the docs, specifically the Caddyfile reference, to see how much it can do.
Take a look at Traefik as well - it and Caddy are quite similar, both in terms of being written in Go, as well as feature set (things like builtin Let's Encrypt support)
Thanks very much for that recommendation. It also looks like something I'll use heavily.
Yeah, it's things like this which give me a good kick up the butt and make me ask myself why I'm still messing around with apache proxypass, lol.
I've never used it in production in a serious way, but currently everything that I self-host is fronted by caddy. I love it; as @Adys mentioned, it has some great features for hobbyists! The built in, no-config Let's Encrypt/HTTPS support is also an absolute god-send.
Things like the file manager and markdown rendering are super cool, even though I've not used them.
FWIW I set it up in production here and it still runs the HSReplay.net servers to my knowledge (Stack goes something like Cloudflare => AWS ECS => Docker => Caddy => uwsgi => Django).
Oh wow, you run HSReplay? Small world.
I mean, yes, open source software stacks, yes good, quite. Much web, very cloud.