It will not receive any new feature updates. Please consider using soketi/pws, an all-in-one Pusher server equivalent for Echo Server that is written in C and ported to Node.js by the awesome guys at uNetworking/uWebSockets.js.
This application had implementation flaws by using both Pusher and Socket.IO and was a really bad idea. The versions before the deprecation announcement are still working and available for you to use.
Echo Server is a Docker-ready, multi-scalable Node.js application used to host your own Socket.IO server for Laravel Broadcasting. It is built on top of Socket.IO and has a Pusher-compatible API server beneath, that makes your implementation in Laravel a breeze.
This is a fork of the original Laravel Echo Server package that was heavily modified.
- Echo Server
Renoki Co. and Soketi 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.
The following are required to function properly:
- Node 14.0+
- Redis 6+ (optional)
Additional information on broadcasting with Laravel can be found in the official Broadcasting docs
You can install the package via npm:
npm install -g @soketi/echo-serverFor additional ways of deployment, see Deploying.
You can run Echo Server directly from the CLI:
$ echo-server startYou may declare the parameters using environment variables directly passed in the CLI or at the OS level, or as key-value attributes in an .env file at the root of the project:
$ DEBUG=1 echo-server startWhen using .env, you can prefix them with ECHO_SERVER_ to avoid conflicts with other apps, but consider this optionally:
# Within your .env file
ECHO_SERVER_DEBUG=1Read the extensive environment variables documentation and learn how to configure the entire Echo Server application to suit your needs.
This server has only HTTP REST API compatibility with any Pusher client. This means that you can use the pusher broadcasting driver in Laravel, and point it to the Echo Server and it will work seamlessly on broadcasting events from your backend.
Consider the following example on setting a broadcasting driver to connect to Echo Server:
'socketio' => [
'driver' => 'pusher',
'key' => env('SOCKETIO_APP_KEY'),
'secret' => env('SOCKETIO_APP_SECRET'),
'app_id' => env('SOCKETIO_APP_ID'),
'options' => [
'cluster' => env('SOCKETIO_APP_CLUSTER'),
'encrypted' => true,
'host' => env('SOCKETIO_HOST', '127.0.0.1'),
'port' => env('SOCKETIO_PORT', 6001),
'scheme' => 'http',
'curl_options' => [
CURLOPT_SSL_VERIFYHOST => 0,
CURLOPT_SSL_VERIFYPEER => 0,
],
],
],This is how an usual .env file might look in Laravel. It's really important to seize the access to the Echo Server by usign a firewall and/or choose a good random combination of app ID, app key and app secret so that you are secure.
BROADCAST_DRIVER=socketio
SOCKETIO_HOST=127.0.0.1
SOCKETIO_PORT=6001
SOCKETIO_APP_ID=echo-app
SOCKETIO_APP_KEY=echo-app-key
SOCKETIO_APP_SECRET=echo-app-secret
MIX_SOCKETIO_APP_KEY="${SOCKETIO_APP_KEY}"
# These are the default values to connect to. It's recommended to specify the server an `APPS_LIST`
# or override these values using `APP_DEFAULT_*` keys.
# For production workloads, it's a MUST to change the default values.
ECHO_SERVER_APP_DEFAULT_ID=echo-app
ECHO_SERVER_DEFAULT_KEY=echo-app-key
ECHO_SERVER_DEFAULT_SECRET=echo-app-secretThe given configuration is an example and should not be used on production as-is. Consider the App Management section to learn how to create your own apps or configure a local one for testing purposes.
Starting with 5.4.0, Echo Server supports Encrypted Private Channels. This feature needs extra configuration from your side to make them work, according to the Pusher protocol.
The minimum required soketi-js package is @soketi/soketi-js@^1.4.2. You will be using it instead of Laravel Echo. To get started with the frontend configuration, see Frontend (Client) Configuration.
You will need to configure your frontend client and your event-sending backend client with a master key that will be generated using the OpenSSL CLI:
$ openssl rand -base64 32The generated key by the command will be then used only in your client configurations and the backend application (in a Laravel app - in your broadcasting.php file). These has nothing to do with the server configuration, as finding the key at the server-side will not match with the protocol specifications and will reside a potential security breach.
'socketio' => [
'driver' => 'pusher',
...
'options' => [
...
'encryption_master_key_base64' => 'vwTqW/UBENYBOySubUo8fldlMFvCzOY8BFO5xAgnOus=',
],
],window.Soketi = new Soketi({
...
encryptionMasterKeyBase64: 'vwTqW/UBENYBOySubUo8fldlMFvCzOY8BFO5xAgnOus=',
});You then are free to use the encrypted private channels:
Soketi.encryptedPrivate('top-secret').listen('.new-documents', e => {
//
});Soketi.js is a hard fork of laravel/echo and customized to solve the custom build that Echo Server has. You can use it as a normal Echo client for the Echo Server, while retaining most of the features that are currently presented in the Laravel Broadcasting docs.
Install it via the CLI:
$ npm install --save-dev @soketi/soketi-jsThe Socket.IO client can be easily namespaced by using the SOCKETIO_APP_KEY value, so that it can listen to the echo-app-key namespace:
import Soketi from '@soketi/soketi-js';
window.io = require('socket.io-client');
window.Soketi = new Soketi({
host: window.location.hostname,
key: process.env.MIX_SOCKETIO_APP_KEY, // should be replaced with the App Key
authHost: 'http://127.0.0.1',
authEndpoint: '/broadcasting/auth',
});
// for example
Soketi.join('chat-room.176').listen('.message', event => {
this.messages.push({
message: event.message,
sender: event.user.id,
});
});Apps are used to allow access to clients, as well as to be able to securely publish events to your users by using signatures generated by app secret.
Get started with the extensive documentation on how to implement different app management drivers for your app, with examples.
Echo Server is optimized to work in multi-node or multi-process environments, like Kubernetes or PM2, where horizontal scalability is one of the main core features that can be built upon.
To be able to scale it horizontally, most of the features leverage the Redis database on both node-to-node communication via Pub/Sub and storage via the key-value store that Redis has already built-in.
You can configure Echo Server to run in a horizontal-ready mode by specifying it using an environment variable.
$ REPLICATION_DRIVER=redis echo-server startStatistics are available for each registered app, if opted-in. They are disabled by default, and you can turn them on for each app. Get started with built-in Echo Server statistics managers.
PM2 is not necessarily horizontally scalable by node, but it is by process. Echo Server PM2-ready and can scale to a lot of processes with ease and without running into conflicts.
Automatically after each release, a Docker tag is created with the application running in Node.js, for your ease. You might want to use them to deploy or test Echo Server on Docker, Docker Swarm or Kubernetes, or any other container orchestration environment. Get started with the versioning & Docker usage on DockerHub.
Echo Server can also be deployed as Helm v3 chart. Echo Server has an official Helm chart at charts/echo-server. You will find complete installation steps to configure and run the app on any Kubernetes cluster.
If you run Echo Server standalone in a cluster, at scale, you might run into capacity issues: RAM usage might be near the limit and even if you decide to horizontally scale the pods, new connections might still come to pods that are near-limit and run into OOM at some point.
Running Network Watcher inside the same pod will solve the issues by continuously checking the current pod using the Prometheus client (Prometheus Server is not needed!), labeling the pods that get over a specified threshold.
Please see CONTRIBUTING for details.
If you discover any security related issues, please email alex@renoki.org instead of using the issue tracker.
