mirror of
https://github.com/HDInnovations/UNIT3D-Community-Edition.git
synced 2026-02-08 20:49:10 -06:00
e90a40ade4
In an effort to make upgrading the constantly changing config files easier, Shift defaulted them so you can review the commit diff for changes. Moving forward, you should use ENV variables or create a separate config file to allow the core config files to remain automatically upgradeable.
90 lines
2.7 KiB
PHP
Executable File
90 lines
2.7 KiB
PHP
Executable File
<?php
|
|
|
|
return [
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Default Queue Connection Name
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| Laravel's queue API supports an assortment of back-ends via a single
|
|
| API, giving you convenient access to each back-end using the same
|
|
| syntax for every one. Here you may define a default connection.
|
|
|
|
|
*/
|
|
|
|
'default' => env('QUEUE_CONNECTION', 'sync'),
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| 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.
|
|
|
|
|
| Drivers: "sync", "database", "beanstalkd", "sqs", "redis", "null"
|
|
|
|
|
*/
|
|
|
|
'connections' => [
|
|
|
|
'sync' => [
|
|
'driver' => 'sync',
|
|
],
|
|
|
|
'database' => [
|
|
'driver' => 'database',
|
|
'table' => 'jobs',
|
|
'queue' => 'default',
|
|
'retry_after' => 90,
|
|
],
|
|
|
|
'beanstalkd' => [
|
|
'driver' => 'beanstalkd',
|
|
'host' => 'localhost',
|
|
'queue' => 'default',
|
|
'retry_after' => 90,
|
|
'block_for' => 0,
|
|
],
|
|
|
|
'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'),
|
|
'queue' => env('SQS_QUEUE', 'your-queue-name'),
|
|
'suffix' => env('SQS_SUFFIX'),
|
|
'region' => env('AWS_DEFAULT_REGION', 'us-east-1'),
|
|
],
|
|
|
|
'redis' => [
|
|
'driver' => 'redis',
|
|
'connection' => 'default',
|
|
'queue' => env('REDIS_QUEUE', 'default'),
|
|
'retry_after' => 90,
|
|
'block_for' => 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' => [
|
|
'driver' => env('QUEUE_FAILED_DRIVER', 'database'),
|
|
'database' => env('DB_CONNECTION', 'mysql'),
|
|
'table' => 'failed_jobs',
|
|
],
|
|
|
|
];
|