Tree: 0b0429b389

ari

cron

dev

dnsconf

json

master

shebang

tlsa

u

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

3.1.1

3.1.2

v2.6.9

v3.0.5

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '0b0429b389'

${ noResults }

Commit Graph

6 Commits (0b0429b389c3d1de5dfdb1a103ebba0e2b97c25c)

Author	SHA1	Message	Date
stilez	0b0429b389	more formatting stuff	7 years ago
stilez	4f233cdb19	yet more formatting	7 years ago
stilez	9fdd77875f	More white space/layout changes to please the engine :)	7 years ago
stilez	5612019c0e	replace 4-space tabs -> 2-space tabs Format engine seems to insist on it :)	7 years ago
stilez	ac9ba6a417	Spaces/indents - I think!	7 years ago
stilez	aa75a6d028	Create a draft version of pleskxml API for DNS01 This DNS01 method allows acme.sh to set DNS TXT records using the Plesk XML API described at: https://docs.plesk.com/en-US/12.5/api-rpc/about-xml-api.28709 and more specifically: https://docs.plesk.com/en-US/12.5/api-rpc/reference.28784 This may be needed if the DNS provider doesn't make the standard Plesk API available to a user - in which case, Plesk can't be configured using usual means or RFC1236. But the XML API is often still left accessible, and is well documented, so it can be used instead, for acme.sh purposes. Note that I have tested the API calls work as expected, and is sanely structured, but I'm not an experienced shell coder. So I expect any number of stylistic and other amendments/corrections. It also includes a ton of debug code which won't hurt to leave in while checking. Please help me to knock this module into shape for merging, and be gentle with me on it - I'm sure it needs a lot of attention! Thanks :)	7 years ago