|
|
**Which ports are being used? **
|
|
|
The gateway listens only on port 11000 (can be changed in main.cpp), and talks to Apple and Google via https (Port 443)
|
|
|
|
|
|
**How do I build the push gateway?**
|
|
|
You need to clone the git repo recursively as the jwt lib is included as a git submodule,
|
|
|
so you either do:
|
|
|
|
|
|
`git clone --recursive-submodules https://git.fairkom.net/chat/RocketChatMobilePushGateway`
|
|
|
|
|
|
or
|
|
|
|
|
|
```
|
|
|
git clone https://git.fairkom.net/chat/RocketChatMobilePushGateway
|
|
|
git submodule update --init --recursive
|
|
|
```
|
|
|
|
|
|
and make sure that you have build and installed proxygen, or just use the Dockerfile.
|
|
|
|
|
|
In the folder you ran the cmake command in, there should be a binary called rocketChatMobilePushGateway
|
|
|
|
|
|
**How is the reliablity of the push gateway?**
|
|
|
|
|
|
pros:
|
|
|
- the code is very simple, there is not much that could go wrong
|
|
|
- the server is totally stateless, so you could run it 1000x behind a load balancer
|
|
|
- the Proxygen library, is used and developed by Facebook as part of the HHVM as well as there own reverse proxies. The memory consumption per Thread is only about 10MB.
|
|
|
|
|
|
cons:
|
|
|
cons:
|
|
|
- we haven't written any functional tests yet
|
|
|
- to deploy it in a kubernetes cluster, I should change the way the certificates are served
|
|
|
- in case of a very high load, it would maybe necessary to queue the messages and send it bundled to Google like every 1s, which is not the case right now
|
|
|
|
|
|
Feel free to ask for a SLA or support at sales@fairkom.eu |
|
|
\ No newline at end of file |