This package is abandoned and no longer maintained. The author suggests using the soketi/echo-server-core package instead.

Echo Server Core is a Laravel utility package used for Socket.IO-based Echo Server application.

2.1.0 2021-02-23 10:46 UTC

This package is auto-updated.

Last update: 2021-02-27 11:12:17 UTC


CI codecov StyleCI Latest Stable Version Total Downloads Monthly Downloads License

Echo Server Core is a Laravel utility package used for Socket.IO-based Echo Server application.

This driver is meant to be used with renoki-co/echo-server, a fork of Laravel Echo Server.

🤝 Supporting

Renoki Co. on GitHub aims on bringing a lot of open source projects and helpful projects to the world. Developing and maintaining projects everyday is a harsh work and tho, we love it.

If you are using your application in your day-to-day job, on presentation demos, hobby projects or even school projects, spread some kind words about our work or sponsor our work. Kind words will touch our chakras and vibe, while the sponsorships will keep the open source projects alive.


🚀 Installation

You can install the package via composer:

composer require renoki-co/echo-server-core

Publish the config:

$ php artisan vendor:publish --provider="RenokiCo\EchoServer\EchoServerServiceProvider" --tag="config"

Publish the migrations:

$ php artisan vendor:publish --provider="RenokiCo\EchoServer\EchoServerServiceProvider" --tag="migrations"

🙌 Usage

Out-of-the-box, you benefit a small range of features, like registering routes to retrieve the apps by using the api apps manager in Node.js.

If you use the Node.js app in a separate environment or location, the .env configurations we get through the docs will not reflect on Node.js app too, so you should additionally configure the Node.js app.

Apps Manager

Checking the configuration file, you might want to use Echo Server Core's database driver alongside with Echo Server's api apps manager. To do so, all the .env variables are set so that they are compatible with Echo Server's ones, so you can easily implement the variables in .env and make both Core & Node.js app to use the same configuration.

# Set the database driver on Core

# Set the API driver on Node.js app

A soft default is set as array, meaning that the default driver is the same as the Node.js app, but this time, the array is used from the config file:



API Manager Security

Since the calls to retrieve the apps are exposing secrets, a token is required to be established between Core & Echo Server app, so that we make sure only the Echo Server has access to them.

You should change the default token for security reasons. It is backwards compatible with the Node.js app, meaning that this will let know the Node.js app about the token too.


Echo Broadcaster

This package comes with a custom broadcaster that fixes the issues that normally the Pusher broadcaster has. It supports natively the same Pusher configuration from broadcasting.php, but the only thing is that the driver is called socketio, and you need to pass additional parameters:

'socketio' => [
    'driver' => 'socketio',
    'key' => env('ECHO_SERVER_APP_DEFAULT_KEY'),
    'secret' => env('ECHO_SERVER_APP_DEFAULT_SECRET'),
    'app_id' => env('ECHO_SERVER_APP_DEFAULT_ID'),
    'options' => [
        'cluster' => 'mt1',
        'encrypted' => true,
        'host' => env('ECHO_SERVER_HOST', ''),
        'port' => 6001,
        'scheme' => env('ECHO_SERVER_SOCKET_PROTOCOL', 'http'),
        'curl_options' => [
            CURLOPT_SSL_VERIFYHOST => 0,
            CURLOPT_SSL_VERIFYPEER => 0,

🐛 Testing


🤝 Contributing

Please see CONTRIBUTING for details.

🔒 Security

If you discover any security related issues, please email instead of using the issue tracker.

🎉 Credits