StackExchange/dnscontrol
1
1
Fork 0
mirror of https://github.com/StackExchange/dnscontrol.git synced 2025-01-10 01:18:30 +08:00
Code Issues Projects Releases Packages Wiki Activity

DOCS: Update README with GHA and LE news (#1428)

Browse source
This commit is contained in:
Tom Limoncelli 2022-03-01 11:44:41 -05:00 committed by GitHub
parent 363558f369
commit d457bce437
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
README.md
View file

@ -176,13 +176,15 @@ docker run --rm -it --volume="$PWD:/srv/jekyll" --volume="$PWD/vendor/bundle:/us
# (Note: The preview isn't perfect. Links that use the site.github.url variable won't work.
```
## Via Github Actions (GHA)
See [dnscontrol-action](https://github.com/koenrh/dnscontrol-action)
# Depreciation warnings (updated 2022-02-05)
* Provider ACTIVEDIRECTORY_PS is deprecated and will be removed soon. Use MSDNS instead.
* Provider NS1 has no maintainer and is jeapardy of being removed or deactivated if no volunteer steps up soon.
* Call for new volunteers maintainers for CLOUDFLARE_API, GCLOUD, NAMEDOTCOM, ROUTE53, and SOFTLAYER.
* Should we retain Let's Encrypt support? The "get-certs" command (renews certs via Let's Encrypt) has no maintainer. There are other projects that do a better job. We are considering removing this feature in the future. See discussion in https://github.com/StackExchange/dnscontrol/issues/1400
* Let's Encrypt support is frozen and will be removed in early 2023. The "get-certs" command (renews certs via Let's Encrypt) has no maintainer. There are other projects that do a better job. If you don't use this feature, please do not start. If you do use this feature, please plan on migrating to something else. See discussion in https://github.com/StackExchange/dnscontrol/issues/1400
# More info at our web site