Caddy – Open-source web server with automatic HTTPS
caddyserver.com
Caddy – Open-source web server with automatic HTTPS
1–10 of 132 posts
Re: Caddy – Open-source web server with automatic HTTPS
#2Caddy is fantastic. I do the odd freelance contract making touch screen interactives for museums here. These have to run on the local host machine which usually isn't networked and Caddy is perfect for this. The last one I did had a massive DeepZoom/OpenSeaDragon image tileset and Caddy managed to serve that flawlessly where my old go to server Mongoose couldn't keep up.
Re: Caddy – Open-source web server with automatic HTTPS
#3Yes, Caddy is awesome! About 3-4 years ago it made it super-easy (and possible) for me to serve my websites with `https`. Before that, I was using nginx, and the process of obtaining certificates seemed quite complicated. Matt Holt, thank you for creating Caddy.
Re: Caddy – Open-source web server with automatic HTTPS
#4I love Caddy!
It’s so much nicer to configure compared to Nginx.
No plugins needed for automatic TLS certs – it’s bulilt-in.
And it’s written in a memory-safe language – Go. Which also means a single static binary to deploy.
I can warmly recommend it.
Re: Caddy – Open-source web server with automatic HTTPS
#5Been using Caddy now for multiple years and will use it for all future projects. Highly recommended.
Re: Caddy – Open-source web server with automatic HTTPS
#6I love Caddy! It’s so much nicer to configure compared to Nginx. No plugins needed for automatic TLS certs – it’s bulilt-in. And it’s written in a memory-safe language – Go. Which also means a single static binary to deploy. I can warmly recommend it.
Go is not memory safe, not sure where you got that idea. Go programs can absolutely succumb to nil pointer references, memory leaks, etc.
Re: Caddy – Open-source web server with automatic HTTPS
#7Caddy is great, makes it easy to just set something up and go. For some reason I can't put my finger on I was really fighting with getting what I wanted to know out of the documentation initially but either it got better since Caddy 2 released or I just got used to it/Caddy and am no longer fighting "newness".
Re: Caddy – Open-source web server with automatic HTTPS
#8I love Caddy! It’s so much nicer to configure compared to Nginx. No plugins needed for automatic TLS certs – it’s bulilt-in. And it’s written in a memory-safe language – Go. Which also means a single static binary to deploy. I can warmly recommend it.
Go is not memory safe, not sure where you got that idea. Go programs can absolutely succumb to nil pointer references, memory leaks, etc.
Safety can include crashing. It's better than returning subtly incorrect results. Yes, there are nil pointers and unnecessary data structures that people keep around, but that's miles ahead of C where an HTTP request and a missing bounds check can inject new code into the application.
If you have a Go program where user input can be executed as code (no cgo, no unsafe), I'd love to see it.
Re: Caddy – Open-source web server with automatic HTTPS
#9I learned only recently that Apache can do automatic Letsencrypt certificate management, not with some third-party module, but with the bundled mod_md.
Re: Caddy – Open-source web server with automatic HTTPS
#10I love Caddy! It’s so much nicer to configure compared to Nginx. No plugins needed for automatic TLS certs – it’s bulilt-in. And it’s written in a memory-safe language – Go. Which also means a single static binary to deploy. I can warmly recommend it.
Go is not memory safe, not sure where you got that idea. Go programs can absolutely succumb to nil pointer references, memory leaks, etc.
That's type safety, not memory safety.
... But no, Go isn't memory safe, insofar data races can cause memory corruption.