Nils Wisiol
Nils Wisiol
@unuseless, would you be able to provide a PR for this? I'm unfamiliar with the details of npm best practice, your help would be most welcome
This has applications to #513, where, e.g., TLSA records could expire automatically when the certificate expires
Depending on the replication mechanism this information is very hard to obtain, and conflicts with replication plans that we recently introduced (#571). I hence suggest we close this issue as...
`certbot` remembers the settings from the initial call, all you need to do is `certbot renew`, passing the config/log/work directories if applicable. On my system, I'm doing certbot --config-dir certbot/config...
Not yet, but we planning to add this in the near future, as the production API has some rate limitations that may hinder development
@andreasnuesslein thanks to your suggestions #396 is resolved, so this issue here is unblocked :)
Thanks, @andreasnuesslein. Enabling contributors to circumvent the whole docker setup is a really good idea! I have a couple of suggestions: 1. Persist the .env file in the repo --...
Superseded by #609
Above [link](https://desec.io/confirm/renew-domain/invalid==/) still shows: 
> > > > Isn't #373 about import, while this is about export? The idea was to have an endpoint that can GET and POST, possibly even PATCH a zone...