laravel-websockets/config/websockets.php

272 lines
8.9 KiB
PHP
Raw Normal View History

2018-11-22 22:55:39 +00:00
<?php
return [
/*
2020-08-13 10:22:58 +00:00
|--------------------------------------------------------------------------
| Dashboard Settings
|--------------------------------------------------------------------------
|
| You can configure the dashboard settings from here.
|
*/
'dashboard' => [
2020-08-13 10:22:58 +00:00
'port' => env('LARAVEL_WEBSOCKETS_PORT', 6001),
2020-08-13 10:22:58 +00:00
'path' => 'laravel-websockets',
'middleware' => [
'web',
\BeyondCode\LaravelWebSockets\Dashboard\Http\Middleware\Authorize::class,
],
],
'managers' => [
/*
|--------------------------------------------------------------------------
| Application Manager
|--------------------------------------------------------------------------
|
| An Application manager determines how your websocket server allows
| the use of the TCP protocol based on, for example, a list of allowed
| applications.
| By default, it uses the defined array in the config file, but you can
| anytime implement the same interface as the class and add your own
| custom method to retrieve the apps.
|
*/
2020-08-13 11:51:18 +00:00
'app' => \BeyondCode\LaravelWebSockets\Apps\ConfigAppManager::class,
2020-08-13 10:22:58 +00:00
/*
|--------------------------------------------------------------------------
| Channel Manager
|--------------------------------------------------------------------------
|
| When users subscribe or unsubscribe from specific channels,
| the connections are stored to keep track of any interaction with the
| WebSocket server.
| You can however add your own implementation that will help the store
| of the channels alongside their connections.
|
*/
'channel' => \BeyondCode\LaravelWebSockets\WebSockets\Channels\ChannelManagers\ArrayChannelManager::class,
2020-08-13 10:34:12 +00:00
],
2018-12-04 19:27:52 +00:00
/*
2020-08-13 10:34:12 +00:00
|--------------------------------------------------------------------------
| Applications Repository
|--------------------------------------------------------------------------
|
| By default, the only allowed app is the one you define with
| your PUSHER_* variables from .env.
| You can configure to use multiple apps if you need to, or use
| a custom App Manager that will handle the apps from a database, per se.
|
| You can apply multiple settings, like the maximum capacity, enable
| client-to-client messages or statistics.
|
*/
2018-12-01 12:57:02 +00:00
'apps' => [
2018-11-24 00:25:40 +00:00
[
2018-12-01 12:57:02 +00:00
'id' => env('PUSHER_APP_ID'),
2018-11-24 22:52:55 +00:00
'name' => env('APP_NAME'),
'host' => env('PUSHER_APP_HOST'),
2018-12-01 12:57:02 +00:00
'key' => env('PUSHER_APP_KEY'),
2018-12-01 14:47:55 +00:00
'secret' => env('PUSHER_APP_SECRET'),
'path' => env('PUSHER_APP_PATH'),
'capacity' => null,
2018-12-01 15:24:36 +00:00
'enable_client_messages' => false,
2018-12-03 10:58:42 +00:00
'enable_statistics' => true,
2020-08-18 13:04:52 +00:00
'allowed_origins' => [
//
],
2018-11-24 00:25:40 +00:00
],
2018-11-23 21:46:09 +00:00
],
2018-11-27 14:55:30 +00:00
/*
2020-08-13 10:34:12 +00:00
|--------------------------------------------------------------------------
| Maximum Request Size
|--------------------------------------------------------------------------
|
| The maximum request size in kilobytes that is allowed for
| an incoming WebSocket request.
|
*/
2018-12-01 14:53:41 +00:00
'max_request_size_in_kb' => 250,
2018-11-27 14:55:30 +00:00
2018-12-04 09:06:26 +00:00
/*
2020-08-13 10:34:12 +00:00
|--------------------------------------------------------------------------
| SSL Configuration
|--------------------------------------------------------------------------
|
| By default, the configuration allows only on HTTP. For SSL, you need
| to set up the the certificate, the key, and optionally, the passphrase
| for the private key.
| You will need to restart the server for the settings to take place.
|
*/
2020-08-13 10:22:58 +00:00
'ssl' => [
2020-08-13 10:34:12 +00:00
2020-08-13 10:22:58 +00:00
'local_cert' => env('LARAVEL_WEBSOCKETS_SSL_LOCAL_CERT', null),
2018-12-04 09:06:26 +00:00
2020-08-13 10:34:12 +00:00
'capath' => env('LARAVEL_WEBSOCKETS_SSL_CA', null),
2020-08-13 10:22:58 +00:00
'local_pk' => env('LARAVEL_WEBSOCKETS_SSL_LOCAL_PK', null),
'passphrase' => env('LARAVEL_WEBSOCKETS_SSL_PASSPHRASE', null),
2020-08-13 10:34:12 +00:00
'verify_peer' => env('APP_ENV') === 'production',
'allow_self_signed' => env('APP_ENV') !== 'production',
2018-12-04 09:06:26 +00:00
],
2020-08-13 10:55:28 +00:00
/*
|--------------------------------------------------------------------------
| Route Handlers
|--------------------------------------------------------------------------
|
| Here you can specify the route handlers that will take over
| the incoming/outgoing websocket connections. You can extend the
| original class and implement your own logic, alongside
| with the existing logic.
|
*/
'handlers' => [
'websocket' => \BeyondCode\LaravelWebSockets\WebSockets\WebSocketHandler::class,
'trigger_event' => \BeyondCode\LaravelWebSockets\HttpApi\Controllers\TriggerEventController::class,
'fetch_channels' => \BeyondCode\LaravelWebSockets\HttpApi\Controllers\FetchChannelsController::class,
'fetch_channel' => \BeyondCode\LaravelWebSockets\HttpApi\Controllers\FetchChannelController::class,
'fetch_users' => \BeyondCode\LaravelWebSockets\HttpApi\Controllers\FetchUsersController::class,
],
/*
|--------------------------------------------------------------------------
2020-08-13 13:18:14 +00:00
| Broadcasting Replication PubSub
|--------------------------------------------------------------------------
|
| You can enable replication to publish and subscribe to
| messages across the driver.
|
2020-08-13 13:18:14 +00:00
| By default, it is set to 'local', but you can configure it to use drivers
| like Redis to ensure connection between multiple instances of
2020-08-13 13:18:14 +00:00
| WebSocket servers. Just set the driver to 'redis' to enable the PubSub using Redis.
|
*/
2020-08-13 10:53:08 +00:00
'replication' => [
'driver' => env('LARAVEL_WEBSOCKETS_REPLICATION_DRIVER', 'local'),
/*
|--------------------------------------------------------------------------
| Local Replication
|--------------------------------------------------------------------------
|
| Local replication is actually a null replicator, meaning that it
| is the default behaviour of storing the connections into an array.
|
*/
'local' => [
'client' => \BeyondCode\LaravelWebSockets\PubSub\Drivers\LocalClient::class,
'statistics_logger' => \BeyondCode\LaravelWebSockets\Statistics\Logger\MemoryStatisticsLogger::class,
],
/*
|--------------------------------------------------------------------------
| Redis Replication
|--------------------------------------------------------------------------
|
| Redis replication relies on the Redis' Pub/Sub protocol. When users
| are connected across multiple nodes, whenever some event gets triggered
| on one instance, the rest of the instances get the same copy and, in
| case the connected users to other instances are valid to receive
| the event, they will receive it.
|
*/
'redis' => [
'connection' => env('LARAVEL_WEBSOCKETS_REPLICATION_CONNECTION', 'default'),
'client' => \BeyondCode\LaravelWebSockets\PubSub\Drivers\RedisClient::class,
'statistics_logger' => \BeyondCode\LaravelWebSockets\Statistics\Logger\RedisStatisticsLogger::class,
],
],
2018-12-04 19:27:52 +00:00
'statistics' => [
2020-08-13 10:22:58 +00:00
2018-12-04 19:27:52 +00:00
/*
2020-08-13 10:34:12 +00:00
|--------------------------------------------------------------------------
| Statistics Driver
2020-08-13 10:34:12 +00:00
|--------------------------------------------------------------------------
|
| Here you can specify which driver to use to store the statistics to.
| See down below for each driver's setting.
|
| Available: database
2020-08-13 10:34:12 +00:00
|
*/
'driver' => env('LARAVEL_WEBSOCKETS_STATISTICS_DRIVER', 'database'),
'database' => [
'driver' => \BeyondCode\LaravelWebSockets\Statistics\Drivers\DatabaseDriver::class,
'model' => \BeyondCode\LaravelWebSockets\Statistics\Models\WebSocketsStatisticsEntry::class,
],
2018-12-04 19:27:52 +00:00
/*
2020-08-13 10:34:12 +00:00
|--------------------------------------------------------------------------
| Statistics Interval Period
|--------------------------------------------------------------------------
|
| Here you can specify the interval in seconds at which
| statistics should be logged.
|
*/
2020-08-13 10:22:58 +00:00
2018-12-04 19:27:52 +00:00
'interval_in_seconds' => 60,
/*
2020-08-13 10:34:12 +00:00
|--------------------------------------------------------------------------
| Statistics Deletion Period
|--------------------------------------------------------------------------
|
| When the clean-command is executed, all recorded statistics older than
| the number of days specified here will be deleted.
|
*/
2020-08-13 10:22:58 +00:00
2018-12-04 21:22:33 +00:00
'delete_statistics_older_than_days' => 60,
],
2018-12-04 19:27:52 +00:00
];