Browse Source

Update README.md

neil 9 years ago
parent
commit
06e8b869b9
1 changed files with 4 additions and 4 deletions
  1. 4 4
      dnsapi/README.md

+ 4 - 4
dnsapi/README.md

@@ -18,7 +18,7 @@ Ok, let's issue cert now:
 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 `~/.acme.sh/account.conf`, when next time you use cloudflare api, it will reuse this key.
 
 
 
@@ -40,7 +40,7 @@ Ok, let's issue cert now:
 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 `~/.acme.sh/account.conf`, when next time you use dnspod.cn api, it will reuse this key.
 
 
 ## Use Cloudxns.com domain api to automatically issue cert
@@ -61,7 +61,7 @@ Ok, let's issue cert now:
 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 `~/.acme.sh/account.conf`, when next time you use Cloudxns.com api, it will reuse this key.
 
 
 
@@ -71,7 +71,7 @@ If your api is not supported yet,  you can write your own dns api.
 
 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  `~/.acme.sh/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.
 3. Then you can use your api to issue cert like: