You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 26, 2024. It is now read-only.
Merge branch 'develop' of github.com:matrix-org/synapse into anoa/async_is_server_admin_user_can_delete_alias
* 'develop' of github.com:matrix-org/synapse: (382 commits)
Convert http.HTTPStatus objects to their int equivalent (#7188)
Reduce the number of calls to `resource.getrusage` (#7183)
Remove some `run_in_background` calls in replication code (#7203)
Revert "Revert "Merge pull request #7153 from matrix-org/babolivier/sso_whitelist_login_fallback""
Revert "Revert "Improve the UX of the login fallback when using SSO (#7152)""
Revert "Merge pull request #7153 from matrix-org/babolivier/sso_whitelist_login_fallback"
Revert "Improve the UX of the login fallback when using SSO (#7152)"
tweak changelog
1.12.3
Update docstring per review comments
Fix device list update stream ids going backward (#7158)
Fix the debian build in a better way. (#7212)
Fix changelog wording
1.12.2
Pin Pillow>=4.3.0,<7.1.0 to fix dep issue
1.12.1
review comment
1.12.1
Support SAML in the user interactive authentication workflow. (#7102)
Allow admins to create aliases when they are not in the room (#7191)
...
There is currently no port for OpenBSD. Additionally, OpenBSD's security
180
191
settings require a slightly more difficult installation process.
181
192
182
-
XXX: I suspect this is out of date.
193
+
(XXX: I suspect this is out of date)
183
194
184
195
1. Create a new directory in `/usr/local` called `_synapse`. Also, create a
185
196
new user called `_synapse` and set that directory as the new user's home.
186
197
This is required because, by default, OpenBSD only allows binaries which need
187
198
write and execute permissions on the same memory space to be run from
188
199
`/usr/local`.
189
200
2.`su` to the new `_synapse` user and change to their home directory.
190
-
3. Create a new virtualenv: `virtualenv -p python2.7 ~/.synapse`
201
+
3. Create a new virtualenv: `virtualenv -p python3 ~/.synapse`
191
202
4. Source the virtualenv configuration located at
192
203
`/usr/local/_synapse/.synapse/bin/activate`. This is done in `ksh` by
193
204
using the `.` command, rather than `bash`'s `source`.
@@ -208,45 +219,6 @@ be found at https://docs.microsoft.com/en-us/windows/wsl/install-win10 for
208
219
Windows 10 and https://docs.microsoft.com/en-us/windows/wsl/install-on-server
209
220
for Windows Server.
210
221
211
-
### Troubleshooting Installation
212
-
213
-
XXX a bunch of this is no longer relevant.
214
-
215
-
Synapse requires pip 8 or later, so if your OS provides too old a version you
216
-
may need to manually upgrade it::
217
-
218
-
sudo pip install --upgrade pip
219
-
220
-
Installing may fail with `Could not find any downloads that satisfy the requirement pymacaroons-pynacl (from matrix-synapse==0.12.0)`.
221
-
You can fix this by manually upgrading pip and virtualenv::
222
-
223
-
sudo pip install --upgrade virtualenv
224
-
225
-
You can next rerun `virtualenv -p python3 synapse` to update the virtual env.
226
-
227
-
Installing may fail during installing virtualenv with `InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. For more information, see https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwarning.`
228
-
You can fix this by manually installing ndg-httpsclient::
229
-
230
-
pip install --upgrade ndg-httpsclient
231
-
232
-
Installing may fail with `mock requires setuptools>=17.1. Aborting installation`.
233
-
You can fix this by upgrading setuptools::
234
-
235
-
pip install --upgrade setuptools
236
-
237
-
If pip crashes mid-installation for reason (e.g. lost terminal), pip may
238
-
refuse to run until you remove the temporary installation directory it
239
-
created. To reset the installation::
240
-
241
-
rm -rf /tmp/pip_install_matrix
242
-
243
-
pip seems to leak *lots* of memory during installation. For instance, a Linux
244
-
host with 512MB of RAM may run out of memory whilst installing Twisted. If this
245
-
happens, you will have to individually install the dependencies which are
246
-
failing, e.g.::
247
-
248
-
pip install twisted
249
-
250
222
## Prebuilt packages
251
223
252
224
As an alternative to installing from source, prebuilt packages are available
@@ -305,7 +277,7 @@ For `buster` and `sid`, Synapse is available in the Debian repositories and
305
277
it should be possible to install it with simply:
306
278
307
279
```
308
-
sudo apt install matrix-synapse
280
+
sudo apt install matrix-synapse
309
281
```
310
282
311
283
There is also a version of `matrix-synapse` in `stretch-backports`. Please see
@@ -366,15 +338,17 @@ sudo pip install py-bcrypt
366
338
367
339
Synapse can be found in the void repositories as 'synapse':
368
340
369
-
xbps-install -Su
370
-
xbps-install -S synapse
341
+
```
342
+
xbps-install -Su
343
+
xbps-install -S synapse
344
+
```
371
345
372
346
### FreeBSD
373
347
374
348
Synapse can be installed via FreeBSD Ports or Packages contributed by Brendan Molloy from:
375
349
376
350
- Ports: `cd /usr/ports/net-im/py-matrix-synapse && make install clean`
377
-
- Packages: `pkg install py27-matrix-synapse`
351
+
- Packages: `pkg install py37-matrix-synapse`
378
352
379
353
380
354
### NixOS
@@ -388,15 +362,17 @@ Once you have installed synapse as above, you will need to configure it.
388
362
389
363
## TLS certificates
390
364
391
-
The default configuration exposes a single HTTP port: http://localhost:8008. It
392
-
is suitable for local testing, but for any practical use, you will either need
393
-
to enable a reverse proxy, or configure Synapse to expose an HTTPS port.
365
+
The default configuration exposes a single HTTP port on the local
366
+
interface: `http://localhost:8008`. It is suitable for local testing,
367
+
but for any practical use, you will need Synapse's APIs to be served
368
+
over HTTPS.
394
369
395
-
For information on using a reverse proxy, see
370
+
The recommended way to do so is to set up a reverse proxy on port
371
+
`8448`. You can find documentation on doing so in
396
372
[docs/reverse_proxy.md](docs/reverse_proxy.md).
397
373
398
-
To configure Synapse to expose an HTTPS port, you will need to edit
399
-
`homeserver.yaml`, as follows:
374
+
Alternatively, you can configure Synapse to expose an HTTPS port. To do
375
+
so, you will need to edit `homeserver.yaml`, as follows:
400
376
401
377
* First, under the `listeners` section, uncomment the configuration for the
402
378
TLS-enabled listener. (Remove the hash sign (`#`) at the start of
@@ -409,19 +385,23 @@ To configure Synapse to expose an HTTPS port, you will need to edit
409
385
resources:
410
386
- names: [client, federation]
411
387
```
388
+
412
389
* You will also need to uncomment the `tls_certificate_path` and
413
390
`tls_private_key_path` lines under the `TLS` section. You can either
414
391
point these settings at an existing certificate and key, or you can
Fix single-sign on with CAS systems: pass the same service URL when requesting the CAS ticket and when calling the `proxyValidate` URL. Contributed by @Naugrimm.
0 commit comments