111–120 of 247 posts
Earlier quoted context omitted.
Cloudflare plugin, that does what exactly? You mean like this one? https://github.com/caddy-dns/cloudflare (I'm using it today, works great. Assuming that's what you meant.)
How to use this plugin with a Caddyfile?
tls {
dns cloudflare
}
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 r…
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…
Earlier quoted context omitted.
Yeah, not gonna use just any apt source. I'll pass.
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.
Thanks for pointing out
Earlier quoted context omitted.
How to use this plugin with a Caddyfile?
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.
Error during parsing: getting DNS provider module named 'cloudflare': module not registered: tls.dns.cloudflare
Using latest docker image.
Earlier quoted context omitted.
Yeah, not gonna use just any apt source. I'll pass.
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…
I understand why, but it’s indeed quite a pain.
Hi 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!
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.
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.
Earlier 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