Commit 158f22f7 authored by neil's avatar neil
Browse files

fix compatible for sh. rename api. '-' is not allowed in the function name.

parent eccec5f6
...@@ -1200,7 +1200,7 @@ issue() { ...@@ -1200,7 +1200,7 @@ issue() {
return 1 return 1
fi fi
addcommand="$_currentRoot_add" addcommand="${_currentRoot}_add"
if ! _exists $addcommand ; then if ! _exists $addcommand ; then
_err "It seems that your api file is not correct, it must have a function named: $addcommand" _err "It seems that your api file is not correct, it must have a function named: $addcommand"
return 1 return 1
......
...@@ -15,7 +15,7 @@ export CF_Email="xxxx@sss.com" ...@@ -15,7 +15,7 @@ export CF_Email="xxxx@sss.com"
Ok, let's issue cert now: Ok, let's issue cert now:
``` ```
le.sh --issue --dns dns-cf -d aa.com -d www.aa.com le.sh --issue --dns dns_cf -d aa.com -d www.aa.com
``` ```
The `CF_Key` and `CF_Email` will be saved in `~/.le/account.conf`, when next time you use cloudflare api, it will reuse this key. The `CF_Key` and `CF_Email` will be saved in `~/.le/account.conf`, when next time you use cloudflare api, it will reuse this key.
...@@ -37,7 +37,7 @@ export DP_Key="sADDsdasdgdsf" ...@@ -37,7 +37,7 @@ export DP_Key="sADDsdasdgdsf"
Ok, let's issue cert now: Ok, let's issue cert now:
``` ```
le.sh --issue --dns dns-dp -d aa.com -d www.aa.com le.sh --issue --dns dns_dp -d aa.com -d www.aa.com
``` ```
The `DP_Id` and `DP_Key` will be saved in `~/.le/account.conf`, when next time you use dnspod.cn api, it will reuse this key. The `DP_Id` and `DP_Key` will be saved in `~/.le/account.conf`, when next time you use dnspod.cn api, it will reuse this key.
...@@ -58,7 +58,7 @@ export CX_Secret="sADDsdasdgdsf" ...@@ -58,7 +58,7 @@ export CX_Secret="sADDsdasdgdsf"
Ok, let's issue cert now: Ok, let's issue cert now:
``` ```
le.sh --issue --dns dns-cx -d aa.com -d www.aa.com le.sh --issue --dns dns_cx -d aa.com -d www.aa.com
``` ```
The `CX_Key` and `CX_Secret` will be saved in `~/.le/account.conf`, when next time you use Cloudxns.com api, it will reuse this key. The `CX_Key` and `CX_Secret` will be saved in `~/.le/account.conf`, when next time you use Cloudxns.com api, it will reuse this key.
...@@ -71,15 +71,15 @@ If your api is not supported yet, you can write your own dns api. ...@@ -71,15 +71,15 @@ If your api is not supported yet, you can write your own dns api.
Let's assume you want to name it 'myapi', Let's assume you want to name it 'myapi',
1. Create a bash script named `~/.le/dns-myapi.sh`, 1. Create a bash script named `~/.le/dns_myapi.sh`,
2. In the scrypt, you must have a function named `dns-myapi-add()`. Which will be called by le.sh to add dns records. 2. In the scrypt, you must have a function named `dns_myapi-add()`. Which will be called by le.sh to add dns records.
3. Then you can use your api to issue cert like: 3. Then you can use your api to issue cert like:
``` ```
le.sh --issue --dns dns-myapi -d aa.com -d www.aa.com le.sh --issue --dns dns_myapi -d aa.com -d www.aa.com
``` ```
For more details, please check our sample script: [dns-myapi.sh](dns-myapi.sh) For more details, please check our sample script: [dns_myapi.sh](dns_myapi.sh)
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment