by cmosguy

Laravel Broadcaster for the HTTP Pushstream Nginx Module

211 Stars 18 Forks Last release: Not found 28 Commits 3 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:

HTTP Push-Stream Nginx Module Laravel Broadcast Driver

Thank your for your interest in the HTTP Push-stream Nginx broadcast driver for Laravel. If you are here, it is because you are trying to leverage the latest feature within the Laravel 5.1 broadcasts events for websockets. The HTTP Pushstream Module for Nginx is a powerful Websocket system.

Why use HTTP Pushstream?

If you want to really absorb the power of the capabilities of this module then check out what the dev-ops from Disqus thought in this link:

How does this driver work?

Once you setup all your routes for the pub/sub requests to the HTTP routes in the

directives for Nginx, then you'll be able to quickly open a socket on your client use the pushstream.js and push your broadcasts out using websocket or long-polling.

The pub/sub requests are internally called by the GuzzleHttp package. The

config file will use the pushstream driver where you can control the HTTP requests to the to your pub/sub endpoints.

You can lock down your pub/sub nginx endpoints using the Access Key Module. Here you can configure the key.



  1. Do a composer require get this package:

    composer require cmosguy/laravel-http-pushstream-broadcaster
  2. Next, go into your

    file and add the following lines accordingly.
    refers to websocket root for your HTTP requests pub/sub routes:
    'default' => 'pushstream',

    'pushstream' => [ 'driver' => 'pushstream', 'base_url' => 'http://localhost', 'access_key' => md5('foo'), 'cert' => null // or 'cert' => 'path/to/server.crt' for self-signed certificate ]

  3. In your

    add the following line to your

Sample Nginx Configuration

  1. In your

    file add:
    push_stream_shared_memory_size 32M;
  2. Edit your config file for your routes in the

    server {
    section. Obviously, you need to understand and modify the items below. The following config information is just meant to get you started. If you want a more thorough config check out this:
    location /channels-stats {
        # activate channels statistics mode for this location
    # query string based channel id
    push_stream_channels_path               $arg_id;


    location /pub {

    activate publisher (admin) mode for this location

    push_stream_publisher admin;

    # query string based channel id
    push_stream_channels_path               $arg_id;


    location ~ /sub/(.*) { # activate subscriber (streaming) mode for this location push_stream_subscriber;

    # positional channel path
    push_stream_channels_path                   $1;


    location ~ /ws/(.*) { # activate websocket mode for this location push_stream_subscriber websocket;

    # positional channel path
    push_stream_channels_path                   $1;
    if ($arg_tests = "on") {
      push_stream_channels_path                 "test_$1";
    # store messages in memory
    push_stream_store_messages              on;
    push_stream_websocket_allow_publish     on;
    if ($arg_qs = "on") {
      push_stream_last_received_message_time "$arg_time";
      push_stream_last_received_message_tag  "$arg_tag";
      push_stream_last_event_id              "$arg_eventid";


Locking down the pub/sub endpoint

    location /pub {
       # activate publisher (admin) mode for this location
       push_stream_publisher admin;
       accesskey                on;
       accesskey_hashmethod     md5;
       accesskey_arg            "access_key";
       accesskey_signature      "foo"

    # query string based channel id
    push_stream_channels_path               $arg_id;

Usage in your app

So, once you are finally ready to trigger an event, you can do this easily now by just extending this

in your event handler:
use Illuminate\Queue\SerializesModels;
use Illuminate\Contracts\Broadcasting\ShouldBroadcast;

class SomeEvent implements ShouldBroadcast { use SerializesModels; /** * @var Foo */ public $foo;

public function __construct(Foo $foo)
    $this->foo = $foo;

 * Get the channels the event should be broadcast on.
 * @return array
public function broadcastOn()
    return ['foochannel-'.$this->foo->uuid];


The Client

Please download the pushstream.js from either following locations:

Study the Push Stream Module

At this time the only way to get more information from about the module and the capabilities is directly from the github repository, so do some reading here:

  • See how the pushstream.js example works here:
  • Also read more about the pushstream.js here:


This is by no means the only way to go about how this should work. You need to understand what all the options do and there is definitely a a


Please help me with updating this documentation. If it does not make sense or if you see something stupid let me know. Also, if there is a way to make this extend further and make it more flexible for others, please submit a PR to improve upon these.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.