Code: https://github.com/nginx/nginx-acme Timely as there has been some talk about automating more of Tildes' certificates management. Certbot works well, but would be nice to simplify the setup...
Timely as there has been some talk about automating more of Tildes' certificates management. Certbot works well, but would be nice to simplify the setup and remove that dependency in the future.
IMO Caddy is an amazing piece of software and does everything NGINX does better, at least without performance considerations. I know nginx has a reputation for being performant, though, so I can...
IMO Caddy is an amazing piece of software and does everything NGINX does better, at least without performance considerations. I know nginx has a reputation for being performant, though, so I can imagine that might be a deciding factor.
For my personal stuff, trying to get Caddy to get wildcard carts has been a massive pain in the ass. I think that’s partly a setup and DNS issue, though, but other than that, I don’t really have a...
For my personal stuff, trying to get Caddy to get wildcard carts has been a massive pain in the ass. I think that’s partly a setup and DNS issue, though, but other than that, I don’t really have a reason to switch from Nginx. I have Nginx working and I can just copy/paste configs when I add new subdomains (I self-host services on various subdomains). ¯\_(ツ)_/¯
I don't want to say "too little, too late"....because i consider myself a fan of nginx, and very much welcome this change...but, then again, i have started using Caddy (as others have noted as...
I don't want to say "too little, too late"....because i consider myself a fan of nginx, and very much welcome this change...but, then again, i have started using Caddy (as others have noted as well)...and, i'm really loving Caddy!
I have about a dozen or so domains and assorted websites that live under nginx (and have for many years now), and similar to what @kari noted, i also do alot of copy/pasting of configs to ease management, etc....but that ever so small amount of friction of managing certs via nginx and certbot was the original thing that had me test out Caddy. Using Caddy is still early days for me, so while i love that certs have pretty much almost become a "solved" thing that i don't have to think too much about...now, the challenge i have is simply the learning curve of Caddy.
I think the documentation for Caddy is well-written, but not detailed enough for my liking...Though i take full responsibility that maybe i overthink things too much sometimes...but i sure wish there were more examples of Caddy config details.
Even still, with this new change for nginx...i now have to weigh for my personal websites, while nginx is reputed to be more performant than Caddy...i think (for my traffic volume needs), Caddy might start to win out, and i might start replacing nginx with Caddy. Now, if any of my sites begins to draw tons more traffic, that is when i will review nginx again.
So, again, its great news to hear that nginx is doing this! And, i honestly don't mean to be a poopie head, but, i think i'm already on my way towards standardizing on Caddy - convenience seems to win over performance here! ;-)
Code: https://github.com/nginx/nginx-acme
Timely as there has been some talk about automating more of Tildes' certificates management. Certbot works well, but would be nice to simplify the setup and remove that dependency in the future.
IMO Caddy is an amazing piece of software and does everything NGINX does better, at least without performance considerations. I know nginx has a reputation for being performant, though, so I can imagine that might be a deciding factor.
For my personal stuff, trying to get Caddy to get wildcard carts has been a massive pain in the ass. I think that’s partly a setup and DNS issue, though, but other than that, I don’t really have a reason to switch from Nginx. I have Nginx working and I can just copy/paste configs when I add new subdomains (I self-host services on various subdomains). ¯\_(ツ)_/¯
I don't want to say "too little, too late"....because i consider myself a fan of nginx, and very much welcome this change...but, then again, i have started using Caddy (as others have noted as well)...and, i'm really loving Caddy!
I have about a dozen or so domains and assorted websites that live under nginx (and have for many years now), and similar to what @kari noted, i also do alot of copy/pasting of configs to ease management, etc....but that ever so small amount of friction of managing certs via nginx and certbot was the original thing that had me test out Caddy. Using Caddy is still early days for me, so while i love that certs have pretty much almost become a "solved" thing that i don't have to think too much about...now, the challenge i have is simply the learning curve of Caddy.
I think the documentation for Caddy is well-written, but not detailed enough for my liking...Though i take full responsibility that maybe i overthink things too much sometimes...but i sure wish there were more examples of Caddy config details.
Even still, with this new change for nginx...i now have to weigh for my personal websites, while nginx is reputed to be more performant than Caddy...i think (for my traffic volume needs), Caddy might start to win out, and i might start replacing nginx with Caddy. Now, if any of my sites begins to draw tons more traffic, that is when i will review nginx again.
So, again, its great news to hear that nginx is doing this! And, i honestly don't mean to be a poopie head, but, i think i'm already on my way towards standardizing on Caddy - convenience seems to win over performance here! ;-)