Move from Pusher

Hive Realtime is compatible with Pusher Channels, so moving is a configuration change.

1. Create a Hive Realtime app in the region closest to your users and copy its App ID, Key, Secret and Host.

2. Frontend: keep your pusher-js or Laravel Echo code and add the host options:

   new Pusher('YOUR_APP_KEY', {
     wsHost: 'realtime-eu.dockhive.io',
     wsPort: 443,
     wssPort: 443,
     forceTLS: true,
     enabledTransports: ['ws', 'wss'],
     cluster: 'eu',
   });

3. Server: replace the app ID, key and secret, and set the host (host: 'realtime-eu.dockhive.io' in Node.js, 'host' => ... in PHP, host=... in Python). Remove the cluster option on the server, or keep it; the host wins.

4. Auth endpoints for private and presence channels keep working unchanged: they sign with your new secret.

5. Webhooks: set your webhook URL in the app’s settings. The payload and the X-Pusher-Key / X-Pusher-Signature headers are the same as Pusher’s, so your webhook handler doesn’t change.

Run both side by side while you switch: point a staging build at Hive Realtime first, then production.

What’s supported

Public, private, private encrypted and presence channels; client events; user sign-in and sending to a user; terminating a user’s connections; batch triggers; channel and presence user queries; webhooks (channel occupied/vacated, member added/removed, client events).

Not available yet: the subscription-count event and watchlists.