Closed pmhausen closed 6 months ago
Sure, the caddy binary already includes this plugin, just needs the GUI component and Caddyfile template component added.
Oof this looks complicated. I need outlined what is exactly needed for a self hosted ACME DNS to work. I have no experience with that.
If each domain and subdomain needs an own account, this will be a huge requirement and such a big change I'm not sure I want to do it.
It's not that hard, really. I'm not asking to add the acme-dns backend ;-)
To just use an acme-dns server running somewhere all you need to set are the API URL of that server and a couple of credentials. How to set up these is left as an exercise to the acme-dns admin.
Compare:
User, password, subdomain and ACME DNS URL are to be known and provided a priori completely outside of the scope of the Caddy plugin.
I'll help with a pull-request, I guess.
Oh so its really just those 4 fields? No problemo then, Im adding this soon.
ACME DNS is a self-hosted DNS provider for certificate authorisation. Currently the Caddy plugin does not offer any self hosted solution. OPNsense's os-acme-client can use ACME DNS, too, so I propose to integrate it.
https://github.com/caddy-dns/acmedns
Kind regards, Patrick