
added endpoint /api/v1/users/{id} scope users-read-all Change-Id: Ibe066b728b460052c619a2fcb0e83b8225543a1f Signed-off-by: smarcet <smarcet@gmail.com>
158 lines
5.7 KiB
PHP
158 lines
5.7 KiB
PHP
<?php
|
|
|
|
return [
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Default Queue Driver
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| The Laravel queue API supports a variety of back-ends via an unified
|
|
| API, giving you convenient access to each back-end using the same
|
|
| syntax for each one. Here you may set the default queue driver.
|
|
|
|
|
| Supported: "null", "sync", "database", "beanstalkd",
|
|
| "sqs", "redis"
|
|
|
|
|
*/
|
|
|
|
'default' => env('QUEUE_DRIVER', 'database'),
|
|
'enable_message_broker' => env("ENABLE_MESSAGE_BROKER", false),
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Queue Connections
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| Here you may configure the connection information for each server that
|
|
| is used by your application. A default configuration has been added
|
|
| for each back-end shipped with Laravel. You are free to add more.
|
|
|
|
|
*/
|
|
|
|
'connections' => [
|
|
|
|
'database' => [
|
|
'connection' => env('QUEUE_CONN', ''),
|
|
'database' => env('QUEUE_DATABASE', ''),
|
|
'driver' => 'database',
|
|
'table' => 'queue_jobs',
|
|
'queue' => 'default',
|
|
'expire' => 60,
|
|
],
|
|
// ...
|
|
'message_broker' => [
|
|
|
|
'driver' => 'rabbitmq',
|
|
|
|
'dsn' => env('RABBITMQ_DSN', null),
|
|
|
|
/*
|
|
* Could be one a class that implements \Interop\Amqp\AmqpConnectionFactory for example:
|
|
* - \EnqueueAmqpExt\AmqpConnectionFactory if you install enqueue/amqp-ext
|
|
* - \EnqueueAmqpLib\AmqpConnectionFactory if you install enqueue/amqp-lib
|
|
* - \EnqueueAmqpBunny\AmqpConnectionFactory if you install enqueue/amqp-bunny
|
|
*/
|
|
|
|
'factory_class' => Enqueue\AmqpLib\AmqpConnectionFactory::class,
|
|
|
|
'host' => env('RABBITMQ_HOST', '127.0.0.1'),
|
|
'port' => env('RABBITMQ_PORT', 5672),
|
|
|
|
'vhost' => env('RABBITMQ_VHOST', 'default'),
|
|
'login' => env('RABBITMQ_LOGIN', 'guest'),
|
|
'password' => env('RABBITMQ_PASSWORD', 'guest'),
|
|
|
|
'queue' => env('RABBITMQ_QUEUE', ''),
|
|
|
|
'options' => [
|
|
|
|
'exchange' => [
|
|
|
|
'name' => env('RABBITMQ_EXCHANGE_NAME'),
|
|
|
|
/*
|
|
* Determine if exchange should be created if it does not exist.
|
|
*/
|
|
|
|
'declare' => env('RABBITMQ_EXCHANGE_DECLARE', true),
|
|
|
|
/*
|
|
* Read more about possible values at https://www.rabbitmq.com/tutorials/amqp-concepts.html
|
|
*/
|
|
|
|
'type' => env('RABBITMQ_EXCHANGE_TYPE', \Interop\Amqp\AmqpTopic::TYPE_FANOUT),
|
|
'passive' => env('RABBITMQ_EXCHANGE_PASSIVE', false),
|
|
'durable' => env('RABBITMQ_EXCHANGE_DURABLE', true),
|
|
'auto_delete' => env('RABBITMQ_EXCHANGE_AUTODELETE', true),
|
|
'arguments' => env('RABBITMQ_EXCHANGE_ARGUMENTS'),
|
|
],
|
|
|
|
'queue' => [
|
|
|
|
/*
|
|
* Determine if queue should be created if it does not exist.
|
|
*/
|
|
|
|
'declare' => env('RABBITMQ_QUEUE_DECLARE', false),
|
|
|
|
/*
|
|
* Determine if queue should be binded to the exchange created.
|
|
*/
|
|
|
|
'bind' => env('RABBITMQ_QUEUE_DECLARE_BIND', false),
|
|
|
|
/*
|
|
* Read more about possible values at https://www.rabbitmq.com/tutorials/amqp-concepts.html
|
|
*/
|
|
|
|
'passive' => env('RABBITMQ_QUEUE_PASSIVE', false),
|
|
'durable' => env('RABBITMQ_QUEUE_DURABLE', true),
|
|
'exclusive' => env('RABBITMQ_QUEUE_EXCLUSIVE', false),
|
|
'auto_delete' => env('RABBITMQ_QUEUE_AUTODELETE', false),
|
|
'arguments' => env('RABBITMQ_QUEUE_ARGUMENTS'),
|
|
],
|
|
],
|
|
|
|
/*
|
|
* Determine the number of seconds to sleep if there's an error communicating with rabbitmq
|
|
* If set to false, it'll throw an exception rather than doing the sleep for X seconds.
|
|
*/
|
|
|
|
'sleep_on_error' => env('RABBITMQ_ERROR_SLEEP', 5),
|
|
|
|
/*
|
|
* Optional SSL params if an SSL connection is used
|
|
* Using an SSL connection will also require to configure your RabbitMQ to enable SSL. More details can be founds here: https://www.rabbitmq.com/ssl.html
|
|
*/
|
|
|
|
'ssl_params' => [
|
|
'ssl_on' => env('RABBITMQ_SSL', false),
|
|
'cafile' => env('RABBITMQ_SSL_CAFILE', null),
|
|
'local_cert' => env('RABBITMQ_SSL_LOCALCERT', null),
|
|
'local_key' => env('RABBITMQ_SSL_LOCALKEY', null),
|
|
'verify_peer' => env('RABBITMQ_SSL_VERIFY_PEER', false),
|
|
'passphrase' => env('RABBITMQ_SSL_PASSPHRASE', null),
|
|
],
|
|
|
|
],
|
|
],
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Failed Queue Jobs
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| These options configure the behavior of failed queue job logging so you
|
|
| can control which database and table are used to store the jobs that
|
|
| have failed. You may change them to any database / table you wish.
|
|
|
|
|
*/
|
|
|
|
'failed' => [
|
|
'connection' => env('QUEUE_CONN', ''),
|
|
'database' => env('QUEUE_DATABASE', ''),
|
|
'table' => 'queue_failed_jobs',
|
|
],
|
|
|
|
];
|