2FAuth/config/queue.php

113 lines
3.7 KiB
PHP
Raw Normal View History

2019-05-20 07:37:41 +02:00
<?php
return [
/*
|--------------------------------------------------------------------------
| Default Queue Connection Name
|--------------------------------------------------------------------------
|
2024-06-26 13:50:12 +02:00
| Laravel's queue supports a variety of backends via a single, unified
| API, giving you convenient access to each backend using identical
| syntax for each. The default queue connection is defined below.
2019-05-20 07:37:41 +02:00
|
*/
2024-06-26 13:50:12 +02:00
'default' => env('QUEUE_CONNECTION', 'database'),
2019-05-20 07:37:41 +02:00
/*
|--------------------------------------------------------------------------
| Queue Connections
|--------------------------------------------------------------------------
|
2024-06-26 13:50:12 +02:00
| Here you may configure the connection options for every queue backend
| used by your application. An example configuration is provided for
| each backend supported by Laravel. You're also free to add more.
2019-05-20 07:37:41 +02:00
|
| Drivers: "sync", "database", "beanstalkd", "sqs", "redis", "null"
|
*/
'connections' => [
'sync' => [
'driver' => 'sync',
],
'database' => [
'driver' => 'database',
2024-06-26 13:50:12 +02:00
'connection' => env('DB_QUEUE_CONNECTION'),
'table' => env('DB_QUEUE_TABLE', 'jobs'),
'queue' => env('DB_QUEUE', 'default'),
'retry_after' => (int) env('DB_QUEUE_RETRY_AFTER', 90),
2021-12-02 13:15:53 +01:00
'after_commit' => false,
2019-05-20 07:37:41 +02:00
],
'beanstalkd' => [
'driver' => 'beanstalkd',
2024-06-26 13:50:12 +02:00
'host' => env('BEANSTALKD_QUEUE_HOST', 'localhost'),
'queue' => env('BEANSTALKD_QUEUE', 'default'),
'retry_after' => (int) env('BEANSTALKD_QUEUE_RETRY_AFTER', 90),
2019-05-20 07:37:41 +02:00
'block_for' => 0,
2021-12-02 13:15:53 +01:00
'after_commit' => false,
2019-05-20 07:37:41 +02:00
],
'sqs' => [
'driver' => 'sqs',
'key' => env('AWS_ACCESS_KEY_ID'),
'secret' => env('AWS_SECRET_ACCESS_KEY'),
'prefix' => env('SQS_PREFIX', 'https://sqs.us-east-1.amazonaws.com/your-account-id'),
2022-11-14 17:10:47 +01:00
'queue' => env('SQS_QUEUE', 'default'),
2021-12-02 13:15:53 +01:00
'suffix' => env('SQS_SUFFIX'),
2019-05-20 07:37:41 +02:00
'region' => env('AWS_DEFAULT_REGION', 'us-east-1'),
2021-12-02 13:15:53 +01:00
'after_commit' => false,
2019-05-20 07:37:41 +02:00
],
'redis' => [
'driver' => 'redis',
2024-06-26 13:50:12 +02:00
'connection' => env('REDIS_QUEUE_CONNECTION', 'default'),
2019-05-20 07:37:41 +02:00
'queue' => env('REDIS_QUEUE', 'default'),
2024-06-26 13:50:12 +02:00
'retry_after' => (int) env('REDIS_QUEUE_RETRY_AFTER', 90),
2019-05-20 07:37:41 +02:00
'block_for' => null,
2021-12-02 13:15:53 +01:00
'after_commit' => false,
2019-05-20 07:37:41 +02:00
],
],
2023-08-01 11:26:58 +02:00
/*
|--------------------------------------------------------------------------
| Job Batching
|--------------------------------------------------------------------------
|
| The following options configure the database and table that store job
| batching information. These options can be updated to any database
| connection and table which has been defined by your application.
|
*/
'batching' => [
'database' => env('DB_CONNECTION', 'mysql'),
'table' => 'job_batches',
],
2019-05-20 07:37:41 +02:00
/*
|--------------------------------------------------------------------------
| Failed Queue Jobs
|--------------------------------------------------------------------------
|
| These options configure the behavior of failed queue job logging so you
2024-06-26 13:50:12 +02:00
| can control how and where failed jobs are stored. Laravel ships with
| support for storing failed jobs in a simple file or in a database.
|
| Supported drivers: "database-uuids", "dynamodb", "file", "null"
2019-05-20 07:37:41 +02:00
|
*/
'failed' => [
2021-12-02 13:15:53 +01:00
'driver' => env('QUEUE_FAILED_DRIVER', 'database-uuids'),
2019-05-20 07:37:41 +02:00
'database' => env('DB_CONNECTION', 'mysql'),
'table' => 'failed_jobs',
],
];