Show HN: Caddy 2 • Hacker News Board

Re: Show HN: Caddy 2

#11

Post by avip » Mon, May 04, 2020, 5:57 PM UTC

Started using Caddy because of OOTB ssl support which literally took 5m setup in container.

Have been running Caddy in production for a year with no issues and much rejoice over my 3 loc config which I can literally memorize.

All praise to Caddy's devs gj

Re: Show HN: Caddy 2

#12

Post by someguy101010 » Mon, May 04, 2020, 5:57 PM UTC

mholt wrote: post #9

someguy101010 wrote: post #7

EDIT: No more Telemetry nvm

It's out. The server was shut down months ago and v2 doesn't have a telemetry client at all.

Thanks for letting me know!

Re: Show HN: Caddy 2

#13

Post by schoolornot » Mon, May 04, 2020, 5:58 PM UTC

I somewhat remember the Caddy team having a history of shady behavior: advertisements in headers, hostility towards contributors, telemetry you have to opt-out of. Has any of this changed or has it become worse?

Re: Show HN: Caddy 2

#14

Post by mholt » Mon, May 04, 2020, 5:59 PM UTC

Hi HN -- this is what I've been working on for the last 14 months, with the help of many contributors and the backing of several sponsors. (Thank You!)

Caddy 2 is a fresh new server experience. Some things might take getting used to, like having every site served over HTTPS unless you specify http:// explicitly in your config. But in general, it will feel familiar to v1 in a lot of ways. If you've used v1 before, I recommend going into v2 with a clean-slate using our Getting Started guide: https://caddyserver.com/docs/getting-started

I'm excited to finally get this out there. Let me know what questions you have!

Re: Show HN: Caddy 2

#15

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

schoolornot wrote: post #13

I somewhat remember the Caddy team having a history of shady behavior: advertisements in headers, hostility towards contributors, telemetry you have to opt-out of. Has any of this changed or has it become worse?

The headers was one of the worst days of my life, believe me. I heard your feedback loud and clear and they were removed shortly thereafter... now about 3 years ago: https://caddy.community/t/the-realities-of-being-a-foss-main...

The telemetry server was shut down months ago and v2 has no telemetry client. Although, the counts we gathered were informative. We learned a lot about MITM activity on the Internet, the health and maturity of TLS clients, and how many connections Caddy has secured (trillions, if you're wondering).

As for whether things have gotten worse, I suppose that's up to you!

Re: Show HN: Caddy 2

#16

Post by Tomte » Mon, May 04, 2020, 6:06 PM UTC

Does Caddy request separate certificates for domains served through it, or is it handled using SANs?

Re: Show HN: Caddy 2

#17

Post by tyingq » Mon, May 04, 2020, 6:06 PM UTC

nikivi wrote: post #3

At what point does one use Caddy over writing a server with few lines in Go/Node. A bit confused on the use case of Caddy.

I imagine it's quite a lot more than a few lines of code to correctly handle HEAD requests, ssl/tls, etags, expires headers, and so on.

Re: Show HN: Caddy 2

#18

Post by narrationbox » Mon, May 04, 2020, 6:06 PM UTC

sqs wrote: post #2

Awesome! We use Caddy at Sourcegraph ( https://sourcegraph.com/search?q=caddy+repo:%5Egithub%5C.com... ) and love it. Caddy makes it much easier to run our app in local dev (with HTTPS and other nice things).

Same here! We are huge fans of Caddy at Narration Box (https://narrationbox.com) and we are considering replacing NGINX completely in our Django production stack. (Currently we only use Caddy for development and staging) The author of Caddy, Matt Holt, is a really great person and is extremely responsive on Twitter and GitHub. Highly recommend checking them out.

Re: Show HN: Caddy 2

#19

Post by xrisk » Mon, May 04, 2020, 6:07 PM UTC

Slightly disappointed because they changed the Caddyfile syntax. I think it's a bit more verbose now, compared to v1.

Re: Show HN: Caddy 2

#20

Post by mmalone » Mon, May 04, 2020, 6:11 PM UTC

mholt wrote: post #15

schoolornot wrote: post #13

I somewhat remember the Caddy team having a history of shady behavior: advertisements in headers, hostility towards contributors, telemetry you have to opt-out of. Has any of this changed or has it become worse?

The headers was one of the worst days of my life, believe me. I heard your feedback loud and clear and they were removed shortly thereafter... now about 3 years ago: https://caddy.community/t/the-realities-of-being-a-foss-main... The telemetry server was shut down months ago and v2 has no telemetry client. Although, the counts we gathered were informative. We learned a lot about MITM activity on the Internet, the hea…

I wish there was a better way manage telemetry for open source. We have this problem at smallstep, too. We don’t have any telemetry — nothing is instrumented / nothing phones home — but that means it’s really hard to know which features are popular. Which makes it hard to prioritize. We only find out when something breaks and we can look at the volume of issues, heh.

We ask people to let us know if / how they’re using our stuff, but very few people do. It’s a tough problem.