mirror of
https://github.com/wintercms/winter.git
synced 2024-06-28 05:33:29 +02:00
f6510979cc
Changed from Laravel defaults: - Array configuration items should have their assigner operators aligned and keys should be sorted alphabetically Removed: - database.fetch: Removed from the default in Laravel 5.4 (and originally changed to FETCH_OBJ in 5.3) see770c41552f& https://github.com/laravel/laravel/pull/3815 - filesystems.cloud: Removed from the default in Laravel 8.4.4 since it's not good practice to use Storage::cloud(), should use explicit disk configurations instead. See82213fbf40- services.mandrill: No longer officially supported since < Laravel 6.x; can use the SMTP driver instead - services.sparkport: No longer officially supported in Laravel since < Laravel 6.x or Winter since v1.2 (third party package to reprovide driver is available but config should be manually added when desired.) - services.stripe: Removed in Laravel v5.8.35, see83d2ecc0e9Explicitly not synced: - Some calls to env(), will be addressed by future work on the ConfigWriter - auth.php, will be addressed by future work to bring the Winter auth system more in line with the Laravel one - cors.php, not implemented by default in Winter at the moment, plugins are available - filesystems.php: storage.links & storage.disks.public not included because storage:link is not supported by Winter yet and further thought is needed for its inclusion. - mail.php: markdown - Laravel's markdown mail functionality not verified to work within Winter which has it's own set of email templating logic. May be investigated and included later down the road if desired. - sanctum.php: Laravel Sanctum is an authentication system for Laravel that is completely untested with Winter. Can be evaluated at a later date for inclusion.
94 lines
2.9 KiB
PHP
94 lines
2.9 KiB
PHP
<?php
|
|
|
|
return [
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Default Queue Connection Name
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| Winter'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 Winter. You are free to add more.
|
|
|
|
|
| Drivers: "sync", "database", "beanstalkd", "sqs", "redis", "null"
|
|
|
|
|
*/
|
|
|
|
'connections' => [
|
|
|
|
'sync' => [
|
|
'driver' => 'sync',
|
|
],
|
|
|
|
'database' => [
|
|
'after_commit' => false,
|
|
'driver' => 'database',
|
|
'queue' => 'default',
|
|
'retry_after' => 90,
|
|
'table' => 'jobs',
|
|
],
|
|
|
|
'beanstalkd' => [
|
|
'after_commit' => false,
|
|
'block_for' => 0,
|
|
'driver' => 'beanstalkd',
|
|
'host' => 'localhost',
|
|
'queue' => 'default',
|
|
'retry_after' => 90,
|
|
],
|
|
|
|
'sqs' => [
|
|
'after_commit' => false,
|
|
'driver' => 'sqs',
|
|
'key' => env('AWS_ACCESS_KEY_ID'),
|
|
'prefix' => env('SQS_PREFIX', 'https://sqs.us-east-1.amazonaws.com/your-account-id'),
|
|
'queue' => env('SQS_QUEUE', 'default'),
|
|
'region' => env('AWS_DEFAULT_REGION', 'us-east-1'),
|
|
'secret' => env('AWS_SECRET_ACCESS_KEY'),
|
|
'suffix' => env('SQS_SUFFIX'),
|
|
],
|
|
|
|
'redis' => [
|
|
'after_commit' => false,
|
|
'block_for' => null,
|
|
'connection' => 'default',
|
|
'driver' => 'redis',
|
|
'queue' => env('REDIS_QUEUE', 'default'),
|
|
'retry_after' => 90,
|
|
],
|
|
|
|
],
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| 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' => [
|
|
'database' => env('DB_CONNECTION', 'mysql'),
|
|
'driver' => env('QUEUE_FAILED_DRIVER', 'database-uuids'),
|
|
'table' => 'failed_jobs',
|
|
],
|
|
|
|
];
|