Install Pusher and Laravel broadcast components and configure BROADCAST_DRIVER=pusher and QUEUE_CONNECTION; 2. Create an application on the Pusher official website and obtain App Keys, fill in the .env file corresponding to the PUSHER variable; 3. Enable BroadcastServiceProvider in config/app.php and define authorized channels in routes/channels.php; 4. Create an event class that implements the ShouldBroadcast interface, set the broadcast channel and data format, and trigger events in the controller; 5. The front-end introduces Pusher JS and Laravel Echo, initialize the configuration and listen to the corresponding channels; 6. Start the service, log in to the user triggers the event, and verify that the real-time broadcast function is successfully run through the browser console and the Pusher debug panel.
Setting up Pusher with Laravel is straightforward once you know the steps. Pusher allows real-time broadcasting of events in your Laravel app—perfect for notifications, chat apps, or live updates. Here's how to get it working.

? 1. Install Pusher and Laravel Broadcast
First, make sure you have the required packages:
composer requires pusher/pusher-php-server
Laravel comes with broadcasting support, but you need to enable it. In your .env
file, set:

BROADCAST_DRIVER=pusher
Also make sure QUEUE_CONNECTION
is set (usually to sync
or database
)—broadcasting often works alongside queues.
? 2. Configure Pusher Credentials
Go to Pusher.com , create an account (if you don't have one), and create a new app. Note down these values from the "App Keys" section:

-
PUSHER_APP_ID
-
PUSHER_APP_KEY
-
PUSHER_APP_SECRET
-
PUSHER_APP_CLUSTER
Add them to your .env
file:
PUSHER_APP_ID=your_app_id PUSHER_APP_KEY=your_app_key PUSHER_APP_SECRET=your_app_secret PUSHER_APP_CLUSTER=your_cluster
Laravel uses these automatically via the config/broadcasting.php
file.
? Tip: Make sure
PUSHER_APP_KEY
matches what you use in your frontend (eg, in JavaScript).
? 3. Enable Broadcast Service Provider
In config/app.php
, uncomment this line in the providers
array:
App\Providers\BroadcastServiceProvider::class,
This registers the routes and logic for broadcasting.
Then, in routes/channels.php
, you can define broadcast authorization routes (eg, for private channels).
Example:
Broadcast::channel('user.{id}', function ($user, $id) { return (int) $user->id === (int) $id; });
? 4. Create and Broadcast an Event
Generate an event:
php artisan make:event NotificationSent
Open the event file ( app/Events/NotificationSent.php
) and implement ShouldBroadcast
:
<?php namespace App\Events; use Illuminate\Broadcasting\Channel; use Illuminate\Broadcasting\InteractsWithSockets; use Illuminate\Broadcasting\PresenceChannel; use Illuminate\Broadcasting\PrivateChannel; use Illuminate\Contracts\Broadcasting\ShouldBroadcast; use Illuminate\Foundation\Events\Dispatchable; use Illuminate\Queue\SerializesModels; class NotificationSent implements ShouldBroadcast { use Dispatchable, InteractsWithSockets, SerializesModels; public $message; public function __construct($message) { $this->message = $message; } public function broadcastOn() { return new PrivateChannel('user.' . auth()->id()); // or PublicChannel('notifications') } public function broadcastWith() { return ['message' => $this->message]; } }
Now dispatch the event from a controller:
event(new NotificationSent('Hello, user!'));
? 5. Listen on the Frontend with JavaScript
Include Pusher JS and Laravel Echo in your frontend (eg, in resources/js/bootstrap.js
or Blade):
<script src="https://js.pusher.com/8.2.0/pusher.min.js"></script> <script src="https://cdn.jsdelivr.net/npm/laravel-echo@1.11.3/dist/echo.iife.js"></script>
Initialize Laravel Echo:
<script> window.Echo = new Echo({ broadcaster: 'pusher', key: 'your-pusher-key', // from PUSHER_APP_KEY cluster: 'your-cluster', // eg, 'mt1' encrypted: true, authEndpoint: '/broadcasting/auth', // for private channels auth: { headers: { 'X-CSRF-TOKEN': document.querySelector('meta[name="csrf-token"]').getAttribute('content') } } }); // Listen to private channel Echo.private('user.' userId) .listen('NotificationSent', (e) => { console.log(e.message); }); </script>
Make sure you have the CSRF meta tag in your layout:
<meta name="csrf-token" content="{{ csrf_token() }}">
? 6. Serve and Test
Run your Laravel app:
php artisan serve
Make sure you're logged in (since private channels depend on auth), then trigger the event.
Check the browser console and Laravel logs ( storage/logs/laravel.log
) for errors.
Use Pusher Debug Console (in Pusher dashboard) to see real-time events being sent.
That's it. You've set up real-time broadcasting with Pusher and Laravel. It's not complicated, but the key parts—correct .env
, event setup, auth, and frontend Echo config—must match exactly.
The above is the detailed content of How to set up Pusher with Laravel?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

There are three ways to add custom validation rules in Laravel: using closures, Rule classes, and form requests. 1. Use closures to be suitable for lightweight verification, such as preventing the user name "admin"; 2. Create Rule classes (such as ValidUsernameRule) to make complex logic clearer and maintainable; 3. Integrate multiple rules in form requests and centrally manage verification logic. At the same time, you can set prompts through custom messages methods or incoming error message arrays to improve flexibility and maintainability.

The core methods for Laravel applications to implement multilingual support include: setting language files, dynamic language switching, translation URL routing, and managing translation keys in Blade templates. First, organize the strings of each language in the corresponding folders (such as en, es, fr) in the /resources/lang directory, and define the translation content by returning the associative array; 2. Translate the key value through the \_\_() helper function call, and use App::setLocale() to combine session or routing parameters to realize language switching; 3. For translation URLs, paths can be defined for different languages ??through prefixed routing groups, or route alias in language files dynamically mapped; 4. Keep the translation keys concise and

ToworkeffectivelywithpivottablesinLaravel,firstaccesspivotdatausingwithPivot()orwithTimestamps(),thenupdateentrieswithupdateExistingPivot(),managerelationshipsviadetach()andsync(),andusecustompivotmodelswhenneeded.1.UsewithPivot()toincludespecificcol

Laravelprovidesacleanandflexiblewaytosendnotificationsviamultiplechannelslikeemail,SMS,in-appalerts,andpushnotifications.Youdefinenotificationchannelsinthevia()methodofanotificationclass,andimplementspecificmethodsliketoMail(),toDatabase(),ortoVonage

ServiceProvider is the core mechanism used in the Laravel framework for registering services and initializing logic. You can create a custom ServiceProvider through the Artisan command; 1. The register method is used to bind services, register singletons, set aliases, etc., and other services that have not yet been loaded cannot be called; 2. The boot method runs after all services are registered and is used to register event listeners, view synthesizers, middleware and other logic that depends on other services; common uses include binding interfaces and implementations, registering Facades, loading configurations, registering command-line instructions and view components; it is recommended to centralize relevant bindings to a ServiceProvider to manage, and pay attention to registration

Dependency injection automatically handles class dependencies through service containers in Laravel without manual new objects. Its core is constructor injection and method injection, such as automatically passing in the Request instance in the controller. Laravel parses dependencies through type prompts and recursively creates the required objects. The binding interface and implementation can be used by the service provider to use the bind method, or singleton to bind a singleton. When using it, you need to ensure type prompts, avoid constructor complications, use context bindings with caution, and understand automatic parsing rules. Mastering these can improve code flexibility and maintenance.

The core methods for handling exceptions and recording errors in Laravel applications include: 1. Use the App\Exceptions\Handler class to centrally manage unhandled exceptions, and record or notify exception information through the report() method, such as sending Slack notifications; 2. Use Monolog to configure the log system, set the log level and output method in config/logging.php, and enable error and above level logs in production environment. At the same time, detailed exception information can be manually recorded in report() in combination with the context; 3. Customize the render() method to return a unified JSON format error response, improving the collaboration efficiency of the front and back end of the API. These steps are

Laravel performance optimization can improve application efficiency through four core directions. 1. Use the cache mechanism to reduce duplicate queries, store infrequently changing data through Cache::remember() and other methods to reduce database access frequency; 2. Optimize database from the model to query statements, avoid N 1 queries, specifying field queries, adding indexes, paging processing and reading and writing separation, and reduce bottlenecks; 3. Use time-consuming operations such as email sending and file exporting to queue asynchronous processing, use Supervisor to manage workers and set up retry mechanisms; 4. Use middleware and service providers reasonably to avoid complex logic and unnecessary initialization code, and delay loading of services to improve startup efficiency.
