Migration to / from Pushy Enterprise is simple and involves two changes to your codebase, while supporting graceful migration as users gradually update your app.
In detail, migration requires adding a line of code to your client app(s), modifying the Pushy API hostname in your backend, and re-registering all devices that use your app, while persisting their Pushy Enterprise device token.
The client code addition looks something like this:
Pushy.setEnterpriseConfig("https://your-enterprise-hostname.pushy.me");
Please contact us for specific instructions for your deployment and client platform(s).
To ensure a graceful migration without incurring downtime, your backend needs to be able to differentiate between the Pushy Pro token and the new Pushy Enterprise device token for each user, and support situations where either is missing. For devices that have not yet been assigned an Enterprise device token, continue sending them notifications using their Pushy Pro token, via the Pushy API endpoint (api.pushy.me). For devices that have obtained an Enterprise token, route their notifications through the Enterprise API endpoint (your-enterprise-hostname.pushy.me).
If you don't require a graceful migration, simply start saving the new Pushy Enterprise token on top of the existing Pushy Pro token, and modify your backend code to make calls to the Pushy Enterprise deployment hostname (your-enterprise-hostname.pushy.me).
If you don't require a graceful migration, simply start saving the new Pushy Enterprise token on top of the existing Pushy Pro token, and modify your backend code to make calls to the Pushy Enterprise deployment hostname (your-enterprise-hostname.pushy.me).
Please get in touch if you have any further questions about migration.
Comments
0 comments
Please sign in to leave a comment.