Synapse VS matrix-docker-ansible-deploy

Here: https://github.com/matrix-org/synapse/blob/develop/docs/workers.md

Matrix Server

For synapse it's not possible (https://github.com/matrix-org/synapse/issues/7076). I don't know about the other server implementations

Issue "README claims you can run a "hot spare" synapse, which is incorrect #7076" points to "multi-master setups" in issue Shard master process. #6677 which continues in issue Shard master process. #7593.

Synapse has a docker image...https://github.com/matrix-org/synapse/tree/develop/docker

• Matrix (synapse) for LibreNMS

One of the main methods for adding redundancy to Synapse Matrix is workers, which you can read into here. On top of that, with simple scripting you can set two servers to run the same master Synapse, such that when one goes down, the other spins up, so that updates and such have extremely low downtime. I'm vaguely aware of there being more you can do being those steps as well but I haven't looked further into it.

Initially I started with Matrix-Synapse. The toughest part was figuring out how to setup a subdomain to host my matrix server on, while still being able to point users to the main domain when they sign-up. (@user:example.com instead of @user:matrix.example.com). Once I figured out how delegation worked with a reverse proxy I got it working and figured id try dendrite. Dendrite is the second generation matrix server written in Go and it I think its configuration is easier and its footprint is smaller than matrix-synapse. However since its still a work in progress and its in beta stages some features aren't implemented and there were a few hiccups that made me switch back to matrix-synapse. So when dendrite is good to go I'll definitely be switching to that.

Matrix Docker Ansible Deploy [1] allows me to unify all chat networks that I use under one single server (and, therefore, one single client), avoiding switching windows. I do believe it saved me hundred of hours...

[1] https://github.com/spantaleev/matrix-docker-ansible-deploy

The easiest way to get everything running is by using the ansible playbook to install matrix and all the relevant extras - https://github.com/spantaleev/matrix-docker-ansible-deploy

For example, one of the services I run is a Matrix node, and with it the signal-matrix bridge, since I prefer using Signal through a Matrix client. I install and maintain it using matrix-docker-ansible-deploy. However, the signal-matrix bridge recently silently broke -- I wasn't receiving any messages, and it took me a little while to figure this out.

I also would like to mention this ansible playbook: https://github.com/spantaleev/matrix-docker-ansible-deploy seems that it is pretty powerful and deploys it easily

Thanks that project seems great. Unfortunately it seems non-trivial to get imessage support up and running according to this: https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2173