123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299 |
- <?php
- return [
- /*
- |--------------------------------------------------------------------------
- | Dashboard Settings
- |--------------------------------------------------------------------------
- |
- | You can configure the dashboard settings from here.
- |
- */
- 'dashboard' => [
- 'port' => env('LARAVEL_WEBSOCKETS_PORT', 6001),
- 'domain' => env('LARAVEL_WEBSOCKETS_DOMAIN'),
- 'path' => env('LARAVEL_WEBSOCKETS_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.
- |
- */
- 'app' => \BeyondCode\LaravelWebSockets\Apps\ConfigAppManager::class,
- ],
- /*
- |--------------------------------------------------------------------------
- | 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.
- |
- */
- 'apps' => [
- [
- 'id' => env('PUSHER_APP_ID'),
- 'name' => env('APP_NAME'),
- 'host' => env('PUSHER_APP_HOST'),
- 'key' => env('PUSHER_APP_KEY'),
- 'secret' => env('PUSHER_APP_SECRET'),
- 'path' => env('PUSHER_APP_PATH'),
- 'capacity' => null,
- 'enable_client_messages' => false,
- 'enable_statistics' => false,
- 'allowed_origins' => [
- // env('LARAVEL_WEBSOCKETS_DOMAIN'),
- ],
- ],
- ],
- /*
- |--------------------------------------------------------------------------
- | Broadcasting Replication PubSub
- |--------------------------------------------------------------------------
- |
- | You can enable replication to publish and subscribe to
- | messages across the driver.
- |
- | By default, it is set to 'local', but you can configure it to use drivers
- | like Redis to ensure connection between multiple instances of
- | WebSocket servers. Just set the driver to 'redis' to enable the PubSub using Redis.
- |
- */
- 'replication' => [
- 'mode' => env('WEBSOCKETS_REPLICATION_MODE', 'local'),
- 'modes' => [
- /*
- |--------------------------------------------------------------------------
- | Local Replication
- |--------------------------------------------------------------------------
- |
- | Local replication is actually a null replicator, meaning that it
- | is the default behaviour of storing the connections into an array.
- |
- */
- 'local' => [
- /*
- |--------------------------------------------------------------------------
- | Channel Manager
- |--------------------------------------------------------------------------
- |
- | The channel manager is responsible for storing, tracking and retrieving
- | the channels as long as their members and connections.
- |
- */
- 'channel_manager' => \BeyondCode\LaravelWebSockets\ChannelManagers\LocalChannelManager::class,
- /*
- |--------------------------------------------------------------------------
- | Statistics Collector
- |--------------------------------------------------------------------------
- |
- | The Statistics Collector will, by default, handle the incoming statistics,
- | storing them until they will become dumped into another database, usually
- | a MySQL database or a time-series database.
- |
- */
- 'collector' => \BeyondCode\LaravelWebSockets\Statistics\Collectors\MemoryCollector::class,
- ],
- 'redis' => [
- 'connection' => env('WEBSOCKETS_REDIS_REPLICATION_CONNECTION', 'default'),
- /*
- |--------------------------------------------------------------------------
- | Channel Manager
- |--------------------------------------------------------------------------
- |
- | The channel manager is responsible for storing, tracking and retrieving
- | the channels as long as their members and connections.
- |
- */
- 'channel_manager' => \BeyondCode\LaravelWebSockets\ChannelManagers\RedisChannelManager::class,
- /*
- |--------------------------------------------------------------------------
- | Statistics Collector
- |--------------------------------------------------------------------------
- |
- | The Statistics Collector will, by default, handle the incoming statistics,
- | storing them until they will become dumped into another database, usually
- | a MySQL database or a time-series database.
- |
- */
- 'collector' => \BeyondCode\LaravelWebSockets\Statistics\Collectors\RedisCollector::class,
- ],
- ],
- ],
- 'statistics' => [
- /*
- |--------------------------------------------------------------------------
- | Statistics Store
- |--------------------------------------------------------------------------
- |
- | The Statistics Store is the place where all the temporary stats will
- | be dumped. This is a much reliable store and will be used to display
- | graphs or handle it later on your app.
- |
- */
- 'store' => \BeyondCode\LaravelWebSockets\Statistics\Stores\DatabaseStore::class,
- /*
- |--------------------------------------------------------------------------
- | Statistics Interval Period
- |--------------------------------------------------------------------------
- |
- | Here you can specify the interval in seconds at which
- | statistics should be logged.
- |
- */
- 'interval_in_seconds' => 60,
- /*
- |--------------------------------------------------------------------------
- | Statistics Deletion Period
- |--------------------------------------------------------------------------
- |
- | When the clean-command is executed, all recorded statistics older than
- | the number of days specified here will be deleted.
- |
- */
- 'delete_statistics_older_than_days' => 60,
- ],
- /*
- |--------------------------------------------------------------------------
- | Maximum Request Size
- |--------------------------------------------------------------------------
- |
- | The maximum request size in kilobytes that is allowed for
- | an incoming WebSocket request.
- |
- */
- 'max_request_size_in_kb' => 250,
- /*
- |--------------------------------------------------------------------------
- | 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.
- |
- */
- 'ssl' => [
- 'local_cert' => env('LARAVEL_WEBSOCKETS_SSL_LOCAL_CERT', null),
- 'capath' => env('LARAVEL_WEBSOCKETS_SSL_CA', null),
- 'local_pk' => env('LARAVEL_WEBSOCKETS_SSL_LOCAL_PK', null),
- 'passphrase' => env('LARAVEL_WEBSOCKETS_SSL_PASSPHRASE', null),
- 'verify_peer' => env('APP_ENV') === 'production',
- 'allow_self_signed' => env('APP_ENV') !== 'production',
- ],
- /*
- |--------------------------------------------------------------------------
- | 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\Server\WebSocketHandler::class,
- 'health' => \BeyondCode\LaravelWebSockets\Server\HealthHandler::class,
- 'trigger_event' => \BeyondCode\LaravelWebSockets\API\TriggerEvent::class,
- 'fetch_channels' => \BeyondCode\LaravelWebSockets\API\FetchChannels::class,
- 'fetch_channel' => \BeyondCode\LaravelWebSockets\API\FetchChannel::class,
- 'fetch_users' => \BeyondCode\LaravelWebSockets\API\FetchUsers::class,
- ],
- /*
- |--------------------------------------------------------------------------
- | Promise Resolver
- |--------------------------------------------------------------------------
- |
- | The promise resolver is a class that takes a input value and is
- | able to make sure the PHP code runs async by using ->then(). You can
- | use your own Promise Resolver. This is usually changed when you want to
- | intercept values by the promises throughout the app, like in testing
- | to switch from async to sync.
- |
- */
- 'promise_resolver' => \React\Promise\FulfilledPromise::class,
- ];
|