3 ms·
Why isn’t caddy using the lego library for ACME and does their own stuff? It seems lego has better support for all kind of providers.
by hda111 4y ago
Why isn’t caddy using the lego library for ACME and does their own stuff? It seems lego has better support for all kind of providers.
- francislavoie 4y agoBecause Lego maintainers wouldn't budge when Caddy needed changes made to increase ACME reliability. Matt wrote his own implementation https://github.com/mholt/acmez https://github.com/mholt/acmez and started using that in Caddy soon after. There's a deeper explanation here: https://github.com/caddyserver/certmagic/issues/71 https://github.com/caddyserver/certmagic/issues/71
- hda111 4y agoInteresting. I will have to try it out. From my experience lego is not very reliable so I understand their point.
- mholt 4y agoYeah, lego's API and unreliability were the ultimate driving factors behind writing my own ACME stack. Actually, lego was originally commissioned for the Caddy project -- but then Caddy's needs evolved to having to support enterprises with tens-of-thousands of domains, and lego crippled under that responsibility due to diverging priorities. Lego is primarily used by Traefik now, and Caddy uses CertMagic+ACMEz to provide more robust, reliable certificate management that scales well. I can guarantee CertMagic+ACMEz is the best cert management available in the ecosystem. It won't let you down.