Weave Code
Pubnub Laravel Package
laravel-notification-channels/pubnub
Send Laravel notifications through PubNub realtime messaging. This channel publishes notification payloads to PubNub channels so subscribed clients receive instant updates over WebSockets, with support for per-notifier channel names and publish options.
PubNub Notifications Channel for Laravel
Frequently asked questions about Pubnub
- How do I install the PubNub notification channel for Laravel?
- Install it with Composer using composer require laravel-notification-channels/pubnub. Then configure your PubNub keyset, add the package's PubNub channel class to your notification's via() array, and implement the toPubnub method on the notification. Check the package's Composer constraints against your Laravel and PHP versions before installing.
- Which Laravel and PHP versions does this PubNub channel support?
- The package's last release was in October 2019, so its Laravel and PHP constraints are likely stale. Do not assume support for current Laravel releases or PHP 8 without checking composer.json and running a compatibility spike. In most cases you should expect to update constraints, the PubNub SDK, exception handling, and tests.
- How do I send a Laravel notification through PubNub?
- Create a normal Laravel notification, add the PubNub channel to its via() method, and implement toPubnub to return the message and target PubNub channel data. Send the notification through Laravel's notification system, preferably as a queued notification for real-time delivery. Keep PubNub channel naming and tenant-specific authorization logic out of your domain code.
- What configuration does the PubNub channel need?
- You need a PubNub keyset, typically including publish and subscribe keys plus a secret key, supplied through environment-driven configuration. The package is a thin publish-side adapter, so channel naming and per-user or per-tenant authorization remain application responsibilities. Consult the package README for the exact configuration keys and notification payload shape.
- Does this package support PubNub subscribe or Access Manager?
- The package is described as a publish-side convenience layer for Laravel notifications, not a complete PubNub integration. Do not expect it to manage client subscriptions, token issuance, or PubNub Access Manager authorization. If you need those features, validate them in a spike and plan to implement or extend them in your application or fork.
- Can I queue PubNub notifications and what happens on failure?
- Yes, the channel fits Laravel's queued notification flow, so use queue workers sized for notification bursts. Because the package is thin, you must add your own retry policy, structured logging, dead-letter handling, and idempotency where duplicate publishes matter. PubNub API errors, rotated keys, authorization failures, and oversized payloads should all be handled explicitly.
- Is laravel-notification-channels/pubnub safe for production?
- Treat it as high risk as a long-lived unmodified dependency because the last release was in 2019, adoption is very low, and there are zero dependents. The MIT license allows forking, but your team must own dependency hygiene, Laravel upgrades, PubNub SDK updates, PHP compatibility, and security patches. Roll out to internal or non-critical notifications first and complete an operational and security review before production use.
- How should I test the PubNub notification channel?
- Run a compatibility spike against your target Laravel and PHP versions, then publish a test notification using a non-production PubNub keyset. Mock the PubNub SDK or HTTP layer for unit tests, and add a small integration test that verifies publish, queueing, authorization failures, and payload limits. Static analysis and explicit tests around retries and duplicate delivery are also recommended.
- What are alternatives to this package for realtime Laravel notifications?
- If PubNub is not already strategic, compare it with Pusher, Ably, or an internal WebSocket service before adopting this package. If PubNub is approved, use this package as a reference implementation or wrap and fork it into private application code. Do not adopt it as an unmodified long-term dependency without ownership and a maintenance plan.
- Is laravel-notification-channels/pubnub still maintained?
- The upstream package appears effectively unmaintained: the last release was in October 2019 and adoption is very low. There is no commercial support path for this package, so support depends on community issues and PubNub's own documentation. Before production use, assign internal ownership, document the fork or vendoring strategy, and define an escalation path for PubNub and Laravel upgrades.
Weaver
How can I help you explore Laravel packages today?