mirror of
https://github.com/ProxyPanel/ProxyPanel.git
synced 2026-04-04 19:49:16 +00:00
5be5e48f5e
This update adds Laravel Reverb as the broadcast driver, introduces event classes for node actions and payment status updates, and implements real-time node management (check, geo refresh, reload) with asynchronous jobs and broadcasting. The admin node UI is refactored to use modals and real-time updates via Echo, and frontend assets are updated to support Reverb. Composer and configuration files are updated for Reverb, and install scripts now handle Reverb setup. Payment status updates are now broadcast to the frontend for real-time feedback.
96 lines
3.4 KiB
PHP
96 lines
3.4 KiB
PHP
<?php
|
|
|
|
return [
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Default Reverb Server
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| This option controls the default server used by Reverb to handle
|
|
| incoming messages as well as broadcasting message to all your
|
|
| connected clients. At this time only "reverb" is supported.
|
|
|
|
|
*/
|
|
|
|
'default' => env('REVERB_SERVER', 'reverb'),
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Reverb Servers
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| Here you may define details for each of the supported Reverb servers.
|
|
| Each server has its own configuration options that are defined in
|
|
| the array below. You should ensure all the options are present.
|
|
|
|
|
*/
|
|
|
|
'servers' => [
|
|
|
|
'reverb' => [
|
|
'host' => env('REVERB_SERVER_HOST', '0.0.0.0'),
|
|
'port' => env('REVERB_SERVER_PORT', 8080),
|
|
'path' => env('REVERB_SERVER_PATH', ''),
|
|
'hostname' => env('REVERB_HOST'),
|
|
'options' => [
|
|
'tls' => [],
|
|
],
|
|
'max_request_size' => env('REVERB_MAX_REQUEST_SIZE', 10_000),
|
|
'scaling' => [
|
|
'enabled' => env('REVERB_SCALING_ENABLED', false),
|
|
'channel' => env('REVERB_SCALING_CHANNEL', 'reverb'),
|
|
'server' => [
|
|
'url' => env('REDIS_URL'),
|
|
'host' => env('REDIS_HOST', '127.0.0.1'),
|
|
'port' => env('REDIS_PORT', '6379'),
|
|
'username' => env('REDIS_USERNAME'),
|
|
'password' => env('REDIS_PASSWORD'),
|
|
'database' => env('REDIS_DB', '0'),
|
|
'timeout' => env('REDIS_TIMEOUT', 60),
|
|
],
|
|
],
|
|
'pulse_ingest_interval' => env('REVERB_PULSE_INGEST_INTERVAL', 15),
|
|
'telescope_ingest_interval' => env('REVERB_TELESCOPE_INGEST_INTERVAL', 15),
|
|
],
|
|
|
|
],
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Reverb Applications
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| Here you may define how Reverb applications are managed. If you choose
|
|
| to use the "config" provider, you may define an array of apps which
|
|
| your server will support, including their connection credentials.
|
|
|
|
|
*/
|
|
|
|
'apps' => [
|
|
|
|
'provider' => 'config',
|
|
|
|
'apps' => [
|
|
[
|
|
'key' => env('REVERB_APP_KEY'),
|
|
'secret' => env('REVERB_APP_SECRET'),
|
|
'app_id' => env('REVERB_APP_ID'),
|
|
'options' => [
|
|
'host' => env('REVERB_HOST'),
|
|
'port' => env('REVERB_PORT', env('REVERB_SCHEME', 'https') === 'https' ? 443 : 80),
|
|
'scheme' => env('REVERB_SCHEME', 'https'),
|
|
'useTLS' => env('REVERB_SCHEME', 'https') === 'https',
|
|
],
|
|
'allowed_origins' => ['*'],
|
|
'ping_interval' => env('REVERB_APP_PING_INTERVAL', 60),
|
|
'activity_timeout' => env('REVERB_APP_ACTIVITY_TIMEOUT', 30),
|
|
'max_connections' => env('REVERB_APP_MAX_CONNECTIONS'),
|
|
'max_message_size' => env('REVERB_APP_MAX_MESSAGE_SIZE', 10_000),
|
|
],
|
|
],
|
|
|
|
],
|
|
|
|
];
|