Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integration with a self-hosted synapse #13

Closed
almereyda opened this issue Jan 27, 2017 · 7 comments
Closed

Integration with a self-hosted synapse #13

almereyda opened this issue Jan 27, 2017 · 7 comments

Comments

@almereyda
Copy link

In the case of a self-hosted synapse server, the push gateway is configured to serve the official app.

Can I run my own sygnal next to synapse, and the Riot app autodetects my custom notification service?

A recent blog post also mentioned https://github.com/slp/matrix-pushgw

@Christilut
Copy link

Did you figure this out?

I'm running my own synapse server with a custom made javascript client and I'm trying to get push notifications working to devices that support push (android, ios, chrome). But I can't figure out how to hook up Sygnal to Synapse. I must be missing something but I'm kind of clueless how to actually use Sygnal to send notifications.

Any pointers in the right direction would be great!

@vinzenzweber
Copy link

It is actually the client who tells Synapse that it wants to be contacted via your custom Sygnal server URL. That implies that you don't have to configure anything in the Synapse or Sygnal config files upfront. The client uses the Client-Server API to tell Synapse about the Pusher. Maybe this documentation helps: https://matrix.org/docs/spec/client_server/r0.2.0.html#post-matrix-client-r0-pushers-set

@almereyda
Copy link
Author

Does this mean we can already run our own identity service, without having to rely on mxisd?
In case of considering Docker, I guess synapse and sygnal can both share the same base image?

We currently have few issues with having to use vector.im as IS, since riot.im stopped accepting CORS requests from our domain at some point, probably due to missing configuration.

@dbkr
Copy link
Member

dbkr commented Sep 5, 2018

For clarity, the push gateway is part of your mobile app deployment rather than your home server deployment: each mobile app publishers has their own which has the APNS/GCM private keys for their apps, so it can only use the one that has the relevant private key (@vinzenzweber correctly describes how this works).

@almereyda we should take this somewhere else rather than fill this thread with chat about a different service, but I'd be interested to know which endpoints CORS isn't working on - this doesn't sound intentional. Come chat in #matrix-identity:matrix.org?

@almereyda
Copy link
Author

almereyda commented Sep 6, 2018

I didn't know that channel; joining.

Edit: Can't join, with another CORS error, probably due to an outdated synapse.

@richvdh
Copy link
Member

richvdh commented Sep 20, 2019

sounds like this was a misunderstanding

@richvdh richvdh closed this as completed Sep 20, 2019
@mrtshoot
Copy link

please visit my own sygnal push gateway with docker on https://github.com/mrtshoot/docker-sygnal

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants