1. 24 Sep, 2019 2 commits
  2. 14 Sep, 2019 1 commit
  3. 05 Sep, 2019 1 commit
  4. 11 Aug, 2019 3 commits
  5. 06 Aug, 2019 1 commit
  6. 05 Aug, 2019 1 commit
  7. 31 Jul, 2019 1 commit
  8. 29 Jul, 2019 1 commit
  9. 27 Jul, 2019 1 commit
    • neil's avatar
      sync (#2404) · 55dea4ee
      neil authored
      * support jdcloud.com
      
      * fix format
      
      * ttl 3000
      
      * Escape slashes (#2375)
      
      * Change 1.1.1.1 to 1.0.0.1 to probe compatibility (#2330)
      
      As we can see, 1.1.1.1 is not routed or routed to an Intranet devices due to historical reason. Change 1.1.1.1 to 1.0.0.1 will have a better compatibility. I found this problem on my Tencent Cloud server.
      
      * check empty id
      
      * fix error
      
      * Add dnsapi for Vultr (#2370)
      
      * Add Vultr dns api
      
      * PushOver notifications (#2325)
      
      * PushOver notifications, using AppToken, UserKey, and optional sounds
      
      * fix errors
      
      * added dns api support for hexonet (#1776)
      
      * update
      
      * minor
      
      * support new Cloudflare Token format
      fix https://github.com/Neilpang/acme.sh/issues/2398
      
      * fix wildcard domain name
      
      * add more info
      
      * fix https://github.com/Neilpang/acme.sh/issues/2377
      
      * fix format
      
      * fix format
      55dea4ee
  10. 24 Jul, 2019 1 commit
  11. 13 Jul, 2019 1 commit
  12. 19 Jun, 2019 1 commit
  13. 15 Jun, 2019 1 commit
  14. 14 Jun, 2019 2 commits
  15. 13 Jun, 2019 1 commit
    • Endre Szabo's avatar
      Help text suggests bad practice. · 9b564431
      Endre Szabo authored
      Please remove the phrase `No news is good news.` as it suggests to decide to go on with a bad operational habit.
      
      Why I am stating this is because that `no news` also could mean that:
      - your `cron` daemon stopped working,
      - your MTA has issues (in case or mail notifications of course),
      - anything in between the host running `acme.sh` and your client went wrong.
      
      (... and probably you will not notice in time if `acme.sh` would otherwise send an error notification (if it runs anyway))
      
      If you expect a daily mail (using `--notify-level 3`) you can always be sure that `acme.sh` has ran successfully before. You can also tick the `acme.sh` checkbox in the daily operational report of your enterprise. ;)
      9b564431
  16. 10 Jun, 2019 1 commit
  17. 03 Jun, 2019 1 commit
  18. 02 Jun, 2019 2 commits
  19. 28 May, 2019 1 commit
    • neil's avatar
      sync (#2297) · 09bce5e6
      neil authored
      * Create LICENSE.md
      
      * remove _hostingde_parse_no_strip_whitespace function as this breaks API requests
      
      * Fix sessionid parsing on BSD
      
      * Make travis happy. (SC2020)
      
      * fix for https://github.com/Neilpang/acme.sh/issues/2286
      
      
      
      * Notify mail update (#2293)
      
      * feat: disable e-mail validation if MAIL_NOVALIDATE is set
      
      * fix: expose _MAIL_BIN variable
      
      * fix: call _mail_body and _mail_cmnd directly to make sure that all used variables are exposed
      
      * fix: update notify/mail.sh
      Co-Authored-By: default avatarMatej Mihevc <zuexo@users.noreply.github.com>
      
      * fix: remove useless echo, quote eval
      09bce5e6
  20. 23 May, 2019 1 commit
  21. 17 May, 2019 1 commit
  22. 13 May, 2019 1 commit
  23. 04 May, 2019 4 commits
  24. 29 Apr, 2019 3 commits
  25. 27 Apr, 2019 1 commit
  26. 26 Apr, 2019 1 commit
  27. 21 Apr, 2019 2 commits
  28. 19 Apr, 2019 1 commit
  29. 17 Apr, 2019 1 commit