Reverb Broadcasting Configuration Guide

⌘K
  1. Home
  2. Docs
  3. Xilancer – Freelanc...
  4. Live chat
  5. Reverb Broadcasting Configuration Guide

Reverb Broadcasting Configuration Guide

Thank you for purchasing the Xilancer script from Envato! This guide provides detailed, step-by-step instructions for configuring Reverb as your broadcasting driver to enable live chat features in your application. Reverb is Laravel’s built-in WebSocket server, offering real-time communication without relying on third-party services like Pusher (though Pusher remains an optional alternative).

Prerequisites:

Ensure your Xilancer script is installed and running on a Laravel-compatible server (PHP 8.3+, Composer, and necessary extensions). You have administrative access to the application and server. Reverb requires Laravel 11 or higher; verify your script version meets this requirement. For production, ensure your server supports running background processes (e.g., via Supervisor or systemd).
Configuration Steps:

Open your browser and navigate to the admin login page (e.g., https://xilancer.xgenious.com/admin/).
Enter your admin credentials (username/email and password) and click Login.


After logging in, Click Chat Settings to access the broadcasting configuration options.


In the Chat Settings page, locate the Broadcasting Driver dropdown.
Select Reverb from the options available.


here settings will automatically update your .env file.

Reverb App ID: A unique identifier for your Reverb application. You can generate a random numeric or alphanumeric value (e.g., "290293"). 
Example App ID: 123456.

Reverb App Key: A public key for client-side authentication. Generate a secure, random string (e.g., "ikbkhfz3Jotfkin4koy"). Use a password generator. 
Example App Key: X7k9pLm2nQ8rStUvWxYzXilancerdEfGhIjKlMnOpQr12.

Reverb App Secret: A private key for server-side authentication. Generate a secure, random string (e.g., "fcfn4mtrI33tz0mwaewl"). 
Example App Secret: PqRsTuVwXyZXilancerDeFgHiJkLmNo12.

Reverb Host: The hostname or IP where the Reverb server runs. Use localhost for local development or your domain (e.g., your-domain.com) for production.

Reverb Port: The port for the Reverb server (default is 8080). Choose an open, unused port.

Reverb Scheme: Use http for local testing or https for secure production environments.
Important Notes on App ID and App Key:

You can generate random values for App ID, App Key, and App Secret as they are user-defined in Reverb. They do not need to be obtained from a third-party service. 
Use tools like a password generator or PHP's bin2hex(random_bytes(16)) for secure values.
Ensure the values are unique, secure, and consistent between the admin settings and server configuration to avoid authentication errors.

After filling in the fields, click the Update button to save changes. The .env file will be updated automatically with these settings.


Access your server via SSH or hosting control panel.

Navigate to the Xilancer script root directory (e.g., cd /path/to/Xilancer-script/core/).

Install Reverb if not already set up: Run php artisan reverb:install.

Start the Reverb server:
For testing: Run php artisan reverb:start in the terminal (foreground mode).
For production: Use a process manager like Supervisor. 
Example config (/etc/supervisor/conf.d/reverb.conf):
[program:reverb]
command=php /path/to/Xilancer-script/core/artisan reverb:start --host=0.0.0.0 --port=8080
directory=/path/to/Xilancer-script/core
autostart=true
autorestart=true
user=www-data
numprocs=1
redirect_stderr=true
stdout_logfile=/path/to/Xilancer-script/storage/logs/reverb.log
Apply changes with sudo supervisorctl reload.
Verify the server is running: Check logs or use telnet localhost 8080 (adjust host/port as needed).


Return to the Xilancer and test the live chat (e.g., send a message).

If configured correctly, real-time updates will work.
Monitor logs (storage/logs/laravel.log and Reverb logs) for errors.

For further assistance, refer to the Laravel Reverb documentation at https://laravel.com/docs/reverb or contact support via your Envato purchase. 

Enjoy real-time chatting with the Xilancer script!


🚀 Note: The .env file is automatically updated based on the settings you provide in the admin panel. Ensure no manual edits conflict with these updates.

Was this article helpful to you? No Yes

How can we help?