Show HN: Caddy 2

Post by mholt » Mon, May 04, 2020, 9:57 PM UTC

benhoyt wrote: post #147

benhoyt wrote: post #146

I recently switched my site from using Amazon Linux 1 + Apache + manual setup to Amazon Linux 2 + Caddy 2 + automated Ansible setup. The documentation for Caddy 2 wasn't quite 100% at the time, but it looks like it's in much better shape now. But Caddy 2 just worked, and gave me SSL seamlessly out of the box, zero config. Love it! My entire Caddyfile looks like this: giftyweddings.com { encode gzip reverse_proxy loca…

The one thing I found tricky was getting the systemd config file correct (I'm not a Linux pro). Looks like he's addressed that too, with this README and demo systemd config -- nice! https://github.com/caddyserver/dist/tree/master/init

Post by francislavoie » Mon, May 04, 2020, 10:08 PM UTC

rcarmo wrote: post #137

Looks great. I have fond memories of Caddy 1.x, but I keep looking for a reverse proxy that can do social auth to protect selected endpoints (I was betting on Traefik having an easy to setup extension for that, but 2.x has been a challenge in other ways...). Anyone know if Caddy 2 has any such extension beyond the basic auth provider I see in the docs?

Post by m_sahaf » Mon, May 04, 2020, 10:16 PM UTC

bovermyer wrote: post #152

mholt wrote: post #63

Earlier quoted context omitted.

Thanks for sharing your experience! I'll admit I got bit by a few differences between the v1 Caddyfile and the v2 Caddyfile too. Namely forgetting * at the end of a path _prefix_ matcher. (In Caddy 2, path matches are exact, unless you suffix with a *.)

How can I best share my config and learnings on this?

Post by atonse » Mon, May 04, 2020, 10:38 PM UTC

mholt wrote: post #94

chris_st wrote: post #88

Earlier quoted context omitted.

Sorry for the stupid question, but what is a "memory-safe SSH server"? Thanks!

Not a stupid question, it's not a phrase you hear very often because there isn't... really... one... at all. (Not in mainstream use AFAIK?) Memory safety is a class of guarantees certain software offers you against certain vulnerabilities. Software written in C is generally considered "memory unsafe" since it's hard to write correct C code when managing with memory, so it's easier to find exploits in them that cause…

Post by x3haloed » Mon, May 04, 2020, 11:36 PM UTC

francislavoie wrote: post #134

x3haloed wrote: post #130

Earlier quoted context omitted.

Another piece of feedback: It’s scary to consider using such a crucial piece of software in production when documentation is referred to as “sort of deprecated” and “slightly outdated.”

Because that's the old documentation, from early betas of Caddy v2. The official documentation at https://caddyserver.com/docs/ is up to date, and not deprecated.