|
@@ -4,27 +4,6 @@ If your dns provider doesn't provide api access, you can use our dns alias mode:
|
|
|
|
|
|
https://github.com/Neilpang/acme.sh/wiki/DNS-alias-mode
|
|
|
|
|
|
-## 1. Use Google Cloud DNS API to automatically issue cert
|
|
|
-
|
|
|
-First you need to authenticate to gcloud.
|
|
|
-
|
|
|
-```
|
|
|
-gcloud init
|
|
|
-```
|
|
|
-
|
|
|
-**The `dns_gcloud` script uses the active gcloud configuration and credentials.**
|
|
|
-There is no logic inside `dns_gcloud` to override the project and other settings.
|
|
|
-If needed, create additional [gcloud configurations](https://cloud.google.com/sdk/gcloud/reference/topic/configurations).
|
|
|
-You can change the configuration being used without *activating* it; simply set the `CLOUDSDK_ACTIVE_CONFIG_NAME` environment variable.
|
|
|
-
|
|
|
-To issue a certificate you can:
|
|
|
-```
|
|
|
-export CLOUDSDK_ACTIVE_CONFIG_NAME=default # see the note above
|
|
|
-acme.sh --issue --dns dns_gcloud -d example.com -d '*.example.com'
|
|
|
-```
|
|
|
-
|
|
|
-`dns_gcloud` also supports [DNS alias mode](https://github.com/Neilpang/acme.sh/wiki/DNS-alias-mode).
|
|
|
-
|
|
|
## 1. Use CloudFlare domain API to automatically issue cert
|
|
|
|
|
|
First you need to login to your CloudFlare account to get your API key.
|
|
@@ -897,6 +876,7 @@ acme.sh --issue --dns dns_tele3 -d example.com -d *.example.com
|
|
|
```
|
|
|
|
|
|
The TELE3_Key and TELE3_Secret will be saved in ~/.acme.sh/account.conf and will be reused when needed.
|
|
|
+<<<<<<< HEAD
|
|
|
## 47. Use Euserv.eu API
|
|
|
|
|
|
First you need to login to your euserv.eu account and activate your API Administration (API Verwaltung).
|
|
@@ -918,6 +898,28 @@ acme.sh --issue --dns dns_euserv -d example.com -d *.example.com --insecure
|
|
|
The `EUSERV_Username` and `EUSERV_Password` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
|
|
|
|
|
|
Please report any issues to https://github.com/initit/acme.sh or to <github@initit.de>
|
|
|
+
|
|
|
+## 48. Use Google Cloud DNS API to automatically issue cert
|
|
|
+
|
|
|
+First you need to authenticate to gcloud.
|
|
|
+
|
|
|
+```
|
|
|
+gcloud init
|
|
|
+```
|
|
|
+
|
|
|
+**The `dns_gcloud` script uses the active gcloud configuration and credentials.**
|
|
|
+There is no logic inside `dns_gcloud` to override the project and other settings.
|
|
|
+If needed, create additional [gcloud configurations](https://cloud.google.com/sdk/gcloud/reference/topic/configurations).
|
|
|
+You can change the configuration being used without *activating* it; simply set the `CLOUDSDK_ACTIVE_CONFIG_NAME` environment variable.
|
|
|
+
|
|
|
+To issue a certificate you can:
|
|
|
+```
|
|
|
+export CLOUDSDK_ACTIVE_CONFIG_NAME=default # see the note above
|
|
|
+acme.sh --issue --dns dns_gcloud -d example.com -d '*.example.com'
|
|
|
+```
|
|
|
+
|
|
|
+`dns_gcloud` also supports [DNS alias mode](https://github.com/Neilpang/acme.sh/wiki/DNS-alias-mode).
|
|
|
+
|
|
|
# Use custom API
|
|
|
|
|
|
If your API is not supported yet, you can write your own DNS API.
|
|
@@ -938,4 +940,4 @@ See: https://github.com/Neilpang/acme.sh/wiki/DNS-API-Dev-Guide
|
|
|
|
|
|
# Use lexicon DNS API
|
|
|
|
|
|
-https://github.com/Neilpang/acme.sh/wiki/How-to-use-lexicon-dns-api
|
|
|
+https://github.com/Neilpang/acme.sh/wiki/How-to-use-lexicon-dns-api
|