From 6d67e2f8c53f5391ea20a39135ee5e2aa2b0ed62 Mon Sep 17 00:00:00 2001 From: babolivier Date: Tue, 19 Jul 2022 14:14:03 +0000 Subject: deploy: 6fccd72f42ac76b185cc20ed258792ff94ee81fb --- latest/setup/installation.html | 24 +++++++++++++++--------- 1 file changed, 15 insertions(+), 9 deletions(-) (limited to 'latest/setup/installation.html') diff --git a/latest/setup/installation.html b/latest/setup/installation.html index e9028877b7..fec09fc441 100644 --- a/latest/setup/installation.html +++ b/latest/setup/installation.html @@ -76,7 +76,7 @@ @@ -303,7 +303,9 @@ python -m synapse.app.homeserver \ --generate-config \ --report-stats=[yes|no] -

... substituting an appropriate value for --server-name.

+

... substituting an appropriate value for --server-name and choosing whether +or not to report usage statistics (hostname, Synapse version, uptime, total +users, etc.) to the developers via the --report-stats argument.

This command will generate you a config file that you can then customise, but it will also generate a set of keys for you. These keys will allow your homeserver to identify itself to other homeserver, so don't lose or delete them. It would be @@ -418,11 +420,11 @@ over HTTPS.

Alternatively, you can configure Synapse to expose an HTTPS port. To do so, you will need to edit homeserver.yaml, as follows:

-
  - port: 8448
+
listeners:
+  - port: 8448
     type: http
     tls: true
     resources:
@@ -430,9 +432,13 @@ each line). The relevant lines are like this:
 

 
    
 
  • 
-
    You will also need to uncomment the tls_certificate_path and
-tls_private_key_path lines under the TLS section. You will need to manage
-provisioning of these certificates yourself.
    
+
    You will also need to add the options tls_certificate_path and
+tls_private_key_path. to your configuration file. You will need to manage provisioning of 
+these certificates yourself.
    
+
    • 
+
  • 
+
    You can find more information about these options as well as how to configure synapse in the 
+configuration manual.
    
 
    If you are using your own certificate, be sure to use a .pem file that
 includes the full certificate chain including any intermediate certificates
 (for instance, if using certbot, use fullchain.pem as your certificate, not
-- 
cgit 1.5.1