diff options
| author | Richard van der Hoff <1389908+richvdh@users.noreply.github.com> | 2019-02-05 16:46:28 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-02-05 16:46:28 +0000 |
| commit | 13828f7d5811c6c0de1ccc4d734a68d01a004dec (patch) | |
| tree | c2a6b048762e99412ac22353faded766074421a7 | |
| parent | Actually add ACME docs (diff) | |
| download | synapse-13828f7d5811c6c0de1ccc4d734a68d01a004dec.tar.xz | |
Update docs/ACME.md
Co-Authored-By: anoadragon453 <1342360+anoadragon453@users.noreply.github.com>
| -rw-r--r-- | docs/ACME.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/ACME.md b/docs/ACME.md index f1a0c25697..309296cc0b 100644 --- a/docs/ACME.md +++ b/docs/ACME.md @@ -2,7 +2,7 @@ Synapse v1.0 requires that federation TLS certificates are verifiable by a trusted root CA. If you do not already have a valid certificate for your domain, the easiest -way to get one is with Synapse's new ACME support, which will use the ACME +way to get one is with Synapse's ACME support (new as of Synapse 0.99), which will use the ACME protocol to provision a certificate automatically. By default, certificates will be obtained from the publicly trusted CA Let's Encrypt. @@ -104,4 +104,4 @@ to true under the `acme` section in `homeserver.yaml`: ``` acme: enabled: true -``` \ No newline at end of file +``` |