github-forks
/
acme.sh
mirror of https://github.com/acmesh-official/acme.sh.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
5,754 Commits
9 Branches
44 Tags
26 MiB
dev
ari
master
tlsa
u
shebang
json
dnsconf
cron
1.2.2
1.2.3
2.0.2
2.2.9
2.3.0
2.5.2
2.6.0
2.6.4
2.6.5
2.6.6
2.6.8
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.7.7
2.7.8
2.7.9
2.8.0
2.8.1
2.8.2
2.8.3
2.8.4
2.8.5
2.8.6
2.8.7
2.8.8
2.8.9
2.9.0
3.0.0
3.0.1
3.0.2
3.0.3
3.0.4
3.0.5
3.0.6
3.0.7
3.0.8
3.0.9
3.1.0
v2.6.9
v3.0.5
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '276e089419'
${ noResults }
Commit Graph

15 Commits (276e089419592eabe1f188fdb53d161ab835cf70)

Author SHA1 Message Date
neil 7362e8de4d fix format 4 months ago
PMExtra 2ea37e6a0d refactor(ali): check the result of prepare_ali_credentials 4 months ago
PMExtra 610bb2b85c refactor(ali): set API endpoint for each action 4 months ago
PMExtra fca6e9b932 refactor: Alibaba Cloud API 4 months ago
Sergey Ponomarev 6b7b5caf54 DNS provider API: structured description 
Instead of using comments declare info in a special variable.
Then the variable can be used to print the DNS API provider usage.
The usage can be parsed on UI and show all needed inputs for options.

The info is stored in plain string that it's both human-readable and easy to parse:

    dns_example_info='API name
     An extended description.
     Multiline.
    Domains: list of alternative domains to find
    Site: the dns provider website e.g. example.com
    Docs: Link to ACME.sh wiki for the provider
    Options:
     VARIABLE1 Title for the option1.
     VARIABLE2 Title for the option2. Default "default value".
     VARIABLE3 Title for the option3. Description to show on UI. Optional.
    Issues: Link to a support ticket on https://github.com/acmesh-official/acme.sh
    Author: First Lastname <authoremail@example.com>, Another Author <https://github.com/example>;
    '

Here:
VARIABLE1 will be required.
VARIABLE2 will be required too but will be populated with a "default value".
VARIABLE3 is optional and can be empty.

A DNS provider may have alternative options like CloudFlare may use API KEY or API Token.
You can use a second section OptionsAlt: section.

Some providers may have alternative names or domains e.g. Aliyun and AlibabaCloud.
Add them to Domains: section.

Signed-off-by: Sergey Ponomarev <stokito@gmail.com>
 9 months ago
LJea 27b1dd04c4
improve the compatibility 
Fixed an issue where some embedded devices could not obtain nanoseconds resulting in abnormal parameter coding
 1 year ago
Tony Gravagno eca57beec1
Issue #2850 : grammar corrections for "exists" and "exist". 5 years ago
Boot Lee 950d024a11 fix grep error when txt value begin with - char (#2471) 5 years ago
neilpang 0096ef4ddb fix ali 7 years ago
neilpang b4325026b1 exe 8 years ago
neilpang 1c22c2f76a fix for solaris 8 years ago
neilpang 542d7977db add new _url_encode 8 years ago
klemens 329174b6d9 spelling fixes 8 years ago
neilpang dbd94d047b fix for aliyun api 8 years ago
baiyangliu be39ab32d1 Add DNS API support for aliyun (#410) 
* Add DNS API support for aliyun

* Update README.md

* format

* format

* format

* format...

* format...

* format

* format

* fix bug

* fix bug

* code format

* code format

* fix bug

* just ok...

* fix bug

* fix bug

* fix bug

* change "echo" to "printf"

* fix bug

* code format

* fix bug."head -c" in function _ali_nonce not supported by solaris

* fix bug."head -c" in function _ali_nonce not supported by solaris

* format

* fix bug._ali_nonce not work on solaris

* fix bug. _ali_nonce not work on solaris

* fix bug. _ali_nonce not work on solaris

* add aliyun.com to README.md
 8 years ago