Matrix - Revision history

Johnno: /* Install Synapse */

2022-02-24T21:41:04Z

Install Synapse

2020-12-14T22:29:05Z

2020-12-01T11:05:56Z

Web configuration

2020-11-29T21:34:45Z

Can't load revision 2316

2020-11-29T21:26:04Z

Configuration

Can't load revision 2315

2020-11-29T21:24:19Z

Configuration

Can't load revision 2314

2020-11-29T21:23:16Z

Database

Can't load revision 2313

2020-11-29T21:22:12Z

Well-known URLs

Can't load revision 2312

2020-11-29T21:21:44Z

Reverse Proxy

Can't load revision 2311

2020-11-29T21:20:49Z

Can't load revision 2310

@@ Line 8: / Line 8: @@
 Synapse is the Matrix server, which is a Python 3 daemon using the Twisted libraries. Add the upstream apt repositories:
-  sudo apt install -y apt-transport-https
-  sudo wget -O /etc/apt/trusted.gpg.d/matrix-org-archive-keyring.gpg \
+  apt install -y apt-transport-https
      <nowiki>https://</nowiki>packages.matrix.org/debian/matrix-org-archive-keyring.gpg
   echo "deb <nowiki>https://</nowiki>packages.matrix.org/debian/ $(lsb_release -cs) main" \
-     | sudo tee /etc/apt/sources.list.d/matrix-org.list
+     > /etc/apt/sources.list.d/matrix-org.list
-  sudo apt update
+  apt update
-  sudo apt install matrix-synapse-py3
+  apt install matrix-synapse-py3
 == Web configuration ==

@@ Line 55: / Line 55: @@
 == Database ==
-Synapse can use SQLite, but it's best to use PostgreSQL in production. Create a user and empty database on PostgreSQL. For some (possibly dumb) reason, Synapse requires old C style collation, which means we have to use template0:
+Synapse can use SQLite, but it's best to use [[PostgreSQL]] in production. Create a user and empty database on PostgreSQL. For some (possibly dumb) reason, Synapse requires old C style collation, which means we have to use template0:
   createuser -SDRP ''<dbuser>''

@@ Line 18: / Line 18: @@
 == Web configuration ==
-There are two steps to this, unless we fiddle about using SRV DNS records.
+There are two steps to this.
 === Well-known URLs ===
-First, we need to add two .well-known URLs to the root domain's web (if any), which need to return JSON content. In the <tt>.well-known/matrix</tt> directory, create a file called "server" with:
+This step is not required if DNS SRV records are used instead. Add two .well-known URLs to the root domain's web, which need to return JSON content. In the <tt>.well-known/matrix</tt> directory, create a file called "server" with:
   {"m.server": "matrix.'''example.com''':443"}
@@ Line 41: / Line 41: @@
 === Reverse Proxy ===
-Second, Point Apache or nginx at it as a reverse proxy to localhost:8008 and configure for SSL on port 443. Make sure the .well-known URLs resolve and have useful headers for JSON.
+Second, Point Apache or nginx at it as a reverse proxy to localhost:8008 and configure for SSL on port 443.
   <VirtualHost *:443>
     ServerName matrix.'''example.com'''