README: link to client implementation (#55)

This commit is contained in:
Joona Hoikkala 2018-03-15 13:40:45 +02:00 committed by GitHub
parent cd3a587e43
commit 01f010e35e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -22,6 +22,9 @@ So basically it boils down to **accessibility** and **security**
- Simple deployment (it's Go after all)
## Usage
A Certbot authentication hook for acme-dns is available at: [https://github.com/joohoi/acme-dns-certbot](https://github.com/joohoi/acme-dns-certbot).
[![asciicast](https://asciinema.org/a/94903.png)](https://asciinema.org/a/94903)
Using acme-dns is a three-step process (provided you already have the self-hosted server set up):
@ -217,6 +220,10 @@ use_header = false
header_name = "X-Forwarded-For"
```
## Client
A Certbot authentication hook for acme-dns is available at: [https://github.com/joohoi/acme-dns-certbot](https://github.com/joohoi/acme-dns-certbot).
## Changelog
- v0.4 Clear error messages for bad TXT record content, proper handling of static CNAME records, fixed IP address parsing from the request, added option to disable registration endpoint in the configuration.
- v0.3.2 Dockerfile was fixed for users using autocert feature