2018-11-22 22:55:39 +00:00
|
|
|
<?php
|
|
|
|
|
|
2018-11-24 00:25:40 +00:00
|
|
|
use BeyondCode\LaravelWebSockets\ClientProviders\ConfigClientProvider;
|
|
|
|
|
|
2018-11-22 22:55:39 +00:00
|
|
|
return [
|
|
|
|
|
|
2018-11-24 00:25:40 +00:00
|
|
|
/**
|
|
|
|
|
* This package comes with multi tenancy out of the box. Here you can
|
2018-11-26 08:15:39 +00:00
|
|
|
* configure the different clients that can use the webSockets server.
|
2018-11-23 21:46:09 +00:00
|
|
|
*
|
2018-11-24 00:25:40 +00:00
|
|
|
* You should make sure that the app id is numeric.
|
|
|
|
|
*/
|
2018-11-23 21:46:09 +00:00
|
|
|
'clients' => [
|
2018-11-24 00:25:40 +00:00
|
|
|
[
|
2018-11-24 22:52:55 +00:00
|
|
|
'name' => env('APP_NAME'),
|
2018-11-26 19:55:47 +00:00
|
|
|
'app_id' => env('PUSHER_APP_ID'),
|
|
|
|
|
'app_key' => env('PUSHER_APP_KEY'),
|
|
|
|
|
'app_secret' => env('PUSHER_APP_SECRET')
|
2018-11-24 00:25:40 +00:00
|
|
|
],
|
2018-11-23 21:46:09 +00:00
|
|
|
],
|
|
|
|
|
|
2018-11-24 00:25:40 +00:00
|
|
|
/**
|
|
|
|
|
* This class is responsible for finding the clients. The default provider
|
|
|
|
|
* will use the clients defined in this config file.
|
|
|
|
|
*
|
|
|
|
|
* You can create a custom provider by implementing the
|
|
|
|
|
* `ClientProvier` interface.
|
|
|
|
|
*/
|
|
|
|
|
'client_provider' => ConfigClientProvider::class,
|
2018-11-24 22:52:55 +00:00
|
|
|
|
2018-11-26 07:51:59 +00:00
|
|
|
/*
|
|
|
|
|
* This array contains the hosts of which you want to allow incoming requests.
|
|
|
|
|
* Leave this empty if you want to accepts requests from all hosts.
|
|
|
|
|
*/
|
|
|
|
|
'allowedOrigins' => [
|
2018-11-26 22:03:13 +00:00
|
|
|
//
|
2018-11-26 07:51:59 +00:00
|
|
|
],
|
2018-11-24 22:52:55 +00:00
|
|
|
|
2018-11-26 07:51:59 +00:00
|
|
|
/*
|
|
|
|
|
* Define the optional SSL context for your websocket connections.
|
|
|
|
|
* You can see all available options at: http://php.net/manual/en/context.ssl.php
|
|
|
|
|
*/
|
|
|
|
|
'ssl' => [
|
|
|
|
|
/*
|
|
|
|
|
* Path to local certificate file on filesystem. It must be a PEM encoded file which
|
|
|
|
|
* contains your certificate and private key. It can optionally contain the
|
|
|
|
|
* certificate chain of issuers. The private key also may be contained
|
|
|
|
|
* in a separate file specified by local_pk.
|
|
|
|
|
*/
|
|
|
|
|
'local_cert' => null,
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Path to local private key file on filesystem in case of separate files for
|
|
|
|
|
* certificate (local_cert) and private key.
|
|
|
|
|
*/
|
|
|
|
|
'local_pk' => null,
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Passphrase with which your local_cert file was encoded.
|
|
|
|
|
*/
|
|
|
|
|
'passphrase' => null
|
|
|
|
|
],
|
2018-11-22 22:55:39 +00:00
|
|
|
];
|