3 ms·
I just set it up. Wasn't that difficult: 1. Added a new postgres db and user 2. Added a new dns name 3. Added a new cert for the new dns name 4. Added a new vh
by mike-cardwell 3y ago
I just set it up. Wasn't that difficult:
1. Added a new postgres db and user
2. Added a new dns name
3. Added a new cert for the new dns name
4. Added a new vhost to nginx to proxy to a new port using the new dns name and cert
5. Added a simple docker-compose to my config
6. Added a snippet to my .well-known/matrix/client
Don't imagine it will take much maintenance. Container will be updated along with the rest of my containers, and the existence of the service doesn't change anything for any existing clients that don't support sliding sync.
- Arathorn 3y agoThe most important thing is to keep it updated, as we're fairly rapidly iterating on it, and most of the Element X bugs we've seen have actually turned out to be a stale Sliding Sync proxy deployment. Glad it was fairly straightforward.
- daedric7 3y agoAgree... i don't think there's a time i have "docker compose pull" and a new version hasn't come up. The fact that this is independent of any server implementation (read Synapse) means you can release much more frequent. Choosing to use a proxy here was the right decision.