moepman/acertmgr
1
0
Fork 0
mirror of https://github.com/moepman/acertmgr.git synced 2024-11-16 08:49:14 +01:00
Code Releases Activity
9ca6dae048
acertmgr/docs/acertmgr.yaml

31 lines
1.1 KiB
YAML
Raw Normal View History

setup: Add config examples, deploy readme and arch PKGBUILD
2019-02-25 18:14:03 +01:00
---
docs: cleanup whitespace and remove "---" from json examples
2019-03-21 22:12:53 +01:00
docs: Update examples and README for ACMEv2 API and other changes
2019-03-19 10:45:36 +01:00
# Optional: Authority API endpoint to use
# Legacy ACME v1 API with options:
#api: v1
setup: Add config examples, deploy readme and arch PKGBUILD
2019-02-25 18:14:03 +01:00
#authority: "https://acme-v01.api.letsencrypt.org"
#authority: "https://acme-staging.api.letsencrypt.org"
configuration: Force user to agree to the authorities Terms of Service Authorities (e.g. Let's Encrypt) usually have Terms of Serivce (ToS) that have to be agreed to. Up until this point we automatically indicated agreement to those ToS and sent the necessary value. This commit changes the behaviour to be in line with recommendations from Let's Encrypt that the user themselves have to indicate their agreement by no longer automatically doing so (except for cases of legacy configuration files to provide compatibility). The user can now indicate ToS agreement by either setting the associated configuration variable (authority_tos_agreement) to the required value and/or providing the required value via a command-line parameter (--authority-tos-agreement=<value>/--tos-agreement=<value>/--tos=<value>)
2019-03-20 10:34:59 +01:00
#authority_tos_agreement: "https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf"
docs: cleanup whitespace and remove "---" from json examples
2019-03-21 22:12:53 +01:00
docs: Update examples and README for ACMEv2 API and other changes
2019-03-19 10:45:36 +01:00
# Current (default) ACME v2 API with options:
#api: v2
#authority: "https://acme-v02.api.letsencrypt.org"
#authority: "https://acme-staging-v02.api.letsencrypt.org"
configuration: Force user to agree to the authorities Terms of Service Authorities (e.g. Let's Encrypt) usually have Terms of Serivce (ToS) that have to be agreed to. Up until this point we automatically indicated agreement to those ToS and sent the necessary value. This commit changes the behaviour to be in line with recommendations from Let's Encrypt that the user themselves have to indicate their agreement by no longer automatically doing so (except for cases of legacy configuration files to provide compatibility). The user can now indicate ToS agreement by either setting the associated configuration variable (authority_tos_agreement) to the required value and/or providing the required value via a command-line parameter (--authority-tos-agreement=<value>/--tos-agreement=<value>/--tos=<value>)
2019-03-20 10:34:59 +01:00
authority_tos_agreement: "true" # Indicates you agree to the ToS stated by the API provider
docs: Update examples and README for ACMEv2 API and other changes
2019-03-19 10:45:36 +01:00
#authority_contact_email: "foo@b.ar" # For single addresses
#authority_contact_email: # For multiple addresses
# - "foo@b.ar"
# - "c4f3@b.ar"
setup: Add config examples, deploy readme and arch PKGBUILD
2019-02-25 18:14:03 +01:00
docs: Update examples and README for ACMEv2 API and other changes
2019-03-19 10:45:36 +01:00
# Optional: account_key location. This defaults to "/etc/acertmgr/account.key"
#account_key: "/etc/acertmgr/account.key"
setup: Add config examples, deploy readme and arch PKGBUILD
2019-02-25 18:14:03 +01:00
# Optional: global server_key location. Otherwise separate key per server
docs: Update examples and README for ACMEv2 API and other changes
2019-03-19 10:45:36 +01:00
#server_key: "/etc/acertmgr/server.key"
setup: Add config examples, deploy readme and arch PKGBUILD
2019-02-25 18:14:03 +01:00
# Optional: global challenge handling mode with parameters
#mode: webdir
#webdir: /var/www/acme-challenge/
#mode: standalone
docs: cleanup whitespace and remove "---" from json examples
2019-03-21 22:12:53 +01:00
#port: 13135
Copy Permalink