mirror of
https://github.com/tinode/chat.git
synced 2026-05-07 20:12:42 +00:00
clarity TNPG instructions
This commit is contained in:
@@ -1,11 +1,11 @@
|
||||
# TNPG: Push Gateway
|
||||
|
||||
This is push notifications adapter which communicates with Tinode Push Gateway (TNPG).
|
||||
This is a push notifications adapter which communicates with Tinode Push Gateway (TNPG).
|
||||
|
||||
TNPG is a proprietary service intended to simplify deployment of on-premise installations.
|
||||
Deploying a Tinode server without TNPG requires [configuring Google FCM](../fcm/) with your own credentials, recompiling Android and iOS clients, releasing them to PlayStore and AppStore under your own accounts. It's usually time consuming and relatively complex.
|
||||
|
||||
TNPG solves this problem by allowing you to send push notifications on behalf of Tinode: you hand a notification over to Tinode, Tinode sends it to client using its own credentials and certificates. Internally it uses [Google FCM](https://firebase.google.com/docs/cloud-messaging/) and as such supports the same platforms as FCM. The main advantage of using TNPG over FCM is simplicity of configuration: mobile clients don't have to be recompiled, all is needed is a configuration update on the server.
|
||||
TNPG solves this problem by letting Tinode LLC (the company behind Tinode) to send push notifications on your behalf: you hand a notification over to TNPG, TNPG sends it to the clients using its own credentials and certificates. Internally it uses [Google FCM](https://firebase.google.com/docs/cloud-messaging/) and as such supports the same platforms as FCM. The main advantage of using TNPG over FCM is simplicity of configuration: you can use stock mobile clients with your custom Tinode server, all is needed is a configuration update on the server.
|
||||
|
||||
## Configuring TNPG adapter
|
||||
|
||||
|
||||
Reference in New Issue
Block a user