Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Caddy 2

caddyserver.com

Post reply on HN
Print view View original

121–130 of 247 posts

Re: Show HN: Caddy 2

#121

Post by mholt »

jbverschoor wrote: post #112
gnalck wrote: post #21

Earlier quoted context omitted.

Hey Matt - thanks for creating and maintaining Caddy all these years! Like others have said in this thread, it is so easy to set up and maintain that it really does feel like "magic". In terms of speeding up adoption of Caddy 2, it may be useful to have a list somewhere of the concrete improvements between the two (as I'm sure there are many). A (very) brief look and search around only yielded this article[1] which r…

Adoption for me would be to have an official apt repo :)

I mean, we want one too, but it's ridiculously hard: https://news.ycombinator.com/item?id=23072385

Help? :D

Re: Show HN: Caddy 2

#122

Post by mholt »

francislavoie wrote: post #119
wdavidw wrote: post #109

This new version looks amazing. I was actually looking at it earlier today. I had to postpone my upgrade because I couldn’t find any alternative or how to include the http.git plugin which I rely on. Any direction in that regard will be appreciated. Congratulation for your work.

There's a git plugin for v2 here: https://github.com/vrongmeal/caddygit

Still WIP but very promising, and pure Go too!

Re: Show HN: Caddy 2

#123

Post by francislavoie »

jbverschoor wrote: post #116
francislavoie wrote: post #89

Earlier quoted context omitted.

You may already know this, but it's very tricky to package Golang projects in official debian repos because they require that every dependency be a separate package. This is a ton work both upfront and to maintain in the long-term, so we haven't made much progress on that front. We'd love to get some help from people who are more comfortable with the debian ecosystem though! It's definitely something we want to achie…

So you’re saying that even if your app compiles to a single binary, that’s a requirement? I understand why, but it’s indeed quite a pain.

Yup. It's a bummer. https://go-team.pages.debian.net/packaging.html

Re: Show HN: Caddy 2

#124

Post by stonogo »

mholt wrote: post #40
petre wrote: post #31

Earlier quoted context omitted.

Why did you do it? What have you sought to achieve with it? It's always a head scratcher for me why people building open source tools would put time and effort towards telemetry. Advertisments in HTTP headers? That's a new one. Advertise to whom, devs looking at a browser debug console?

It was for a class during my grad program. It was an academic interest in understanding client behavior on the Internet that wasn't limited to proprietary networks like Cloudflare or Google. We collected some good measurement data -- anonymous, technical, non-personal, etc -- but the terabytes added up and the academic community didn't seem particularly responsive to it in the end. The "opt-in" / "opt-out" depended o…

>Yet nobody cares.

People care about each and every one of those. It's disingenuous to pretend that Caddy was singled out.

Re: Show HN: Caddy 2

#125

Post by mxschmitt »

I really like Caddy and use it e.g. in Try Playwright: https://github.com/mxschmitt/try-playwright/blob/master/fron...

For me as a user, the documentation is sometimes not very clear if it comes to Caddyfile syntax vs. JSON. It would be maybe better to always provide both or configurable via some switch e.g. (maybe its only for me not always fully clear).

-> Great product, nice security settings by default and for me definitely the way to go.

Re: Show HN: Caddy 2

#126

Post by mholt »

nklmilojevic wrote: post #115
mholt wrote: post #111

Earlier quoted context omitted.

tls { dns cloudflare } Replace with your API token, or you can store it in an env variable and use {env.CLOUDFLARE_API_TOKEN} for example.

That's what I already tried and got: Error during parsing: getting DNS provider module named 'cloudflare': module not registered: tls.dns.cloudflare Using latest docker image.

"Latest", as in "1 hour ago" latest, or "15 minutes ago" latest? Because the 2.0 image (not RCs) is needed and I think it only got published a few minutes ago.

Edit: You also need to plug it in.

    xcaddy build --with github.com/caddy-dns/cloudflare

Re: Show HN: Caddy 2

#128

Post by nklmilojevic »

mholt wrote: post #126
nklmilojevic wrote: post #115

Earlier quoted context omitted.

That's what I already tried and got: Error during parsing: getting DNS provider module named 'cloudflare': module not registered: tls.dns.cloudflare Using latest docker image.

"Latest", as in "1 hour ago" latest, or "15 minutes ago" latest? Because the 2.0 image (not RCs) is needed and I think it only got published a few minutes ago. Edit: You also need to plug it in. xcaddy build --with github.com/caddy-dns/cloudflare

I have just tried again, used caddy:latest and got the same error. Didn't mean to take much of your time, I can open up a GitHub issue if it's the better way to resolve this.

EDIT: I have just seen your edit. Will try and report back.

Thanks for your time!

Re: Show HN: Caddy 2

#129

Post by francislavoie »

nklmilojevic wrote: post #128
mholt wrote: post #126

Earlier quoted context omitted.

"Latest", as in "1 hour ago" latest, or "15 minutes ago" latest? Because the 2.0 image (not RCs) is needed and I think it only got published a few minutes ago. Edit: You also need to plug it in. xcaddy build --with github.com/caddy-dns/cloudflare

I have just tried again, used caddy:latest and got the same error. Didn't mean to take much of your time, I can open up a GitHub issue if it's the better way to resolve this. EDIT: I have just seen your edit. Will try and report back. Thanks for your time!

Make sure to run "docker pull caddy"!

Also, see the docs on docker hub: https://hub.docker.com/_/caddy/

You'll need to build Caddy with the builder image to add the DNS plugin, see the section titled "Adding custom Caddy modules".

Re: Show HN: Caddy 2

#130

Post by x3haloed »

mholt wrote: post #27
gnalck wrote: post #21

Earlier quoted context omitted.

Hey Matt - thanks for creating and maintaining Caddy all these years! Like others have said in this thread, it is so easy to set up and maintain that it really does feel like "magic". In terms of speeding up adoption of Caddy 2, it may be useful to have a list somewhere of the concrete improvements between the two (as I'm sure there are many). A (very) brief look and search around only yielded this article[1] which r…

Thanks for the feedback! Glad you have had a good experience with it. That blog post is pretty old. We do have a current upgrade guide here in our docs: https://caddyserver.com/docs/v2-upgrade We also have a (sort of deprecated) wiki with some (slightly outdated) high-level improvements listed: https://github.com/caddyserver/caddy/wiki/v2:-Improvements

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.”
Post reply on HN