Earlier quoted context omitted.
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".
Show HN: Caddy 2
131–140 of 247 posts
Re: Show HN: Caddy 2
#132Earlier quoted context omitted.
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.
It's not a stretch to say that other projects didn't get as much hate for it. It really hurt the project's momentum when there was such a strong reaction against it.
Re: Show HN: Caddy 2
#133Earlier quoted context omitted.
It's not a random source. The package is created by the release script in Caddy's repo: https://github.com/caddyserver/caddy/blob/e051e119d1dff75972... There's ongoing effort to package Caddy into Debian. Until then, this is the alternative as stopgap.
Nowhere on the website old or new is any info available. Thanks for pointing out
Re: Show HN: Caddy 2
#134Earlier quoted context omitted.
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.”
The official documentation at https://caddyserver.com/docs/ is up to date, and not deprecated.
Re: Show HN: Caddy 2
#135Earlier quoted context omitted.
Nowhere on the website old or new is any info available. Thanks for pointing out
I swear I couldn't find that page... been looking for half an hour.
Re: Show HN: Caddy 2
#136Re: Show HN: Caddy 2
#137Anyone know if Caddy 2 has any such extension beyond the basic auth provider I see in the docs?
Re: Show HN: Caddy 2
#138Re: Show HN: Caddy 2
#139Hi mholt!, I am building an ecommerce SaaS.Obviously,i will have each domain pointed to my server.Is Caddy a good choice for automatically getting a certificate for each website?Are there any limitations? Thanks!
Hi! We’ve done this exact same thing and have a technical writeup here: https://ohdear.app/blog/how-we-used-caddy-and-laravels-subdo... Tl:dr: very easy to do, Caddy takes care of 90% of the complexity.
Re: Show HN: Caddy 2
#140What benefits does this provide for the common Nginx usage (reverse proxy to a number of Python/etc application servers)? I see automatic HTTPS and HTTP/2. Am I missing something else notable?