ahmido
8426741068
## Summary - add explicit BaselineSnapshot lifecycle truth with conservative backfill and a shared truth resolver - block baseline compare from building, incomplete, or superseded snapshots and align workspace/tenant UI truth surfaces with effective snapshot state - surface artifact truth separately from operation outcome across baseline profile, snapshot, compare, and operation run pages ## Testing - integrated browser smoke test on the active feature surfaces - `vendor/bin/sail artisan test --compact tests/Feature/Filament/BaselineSnapshotTruthSurfaceTest.php tests/Feature/Filament/BaselineProfileCompareStartSurfaceTest.php` - targeted baseline lifecycle and compare guard coverage added in Pest - `vendor/bin/sail bin pint --dirty --format agent` ## Notes - Livewire v4 compliance preserved - no panel provider registration changes were needed; Laravel 12 providers remain in `bootstrap/providers.php` - global search remains disabled for the affected baseline resources by design - destructive actions remain confirmation-gated; capture and compare actions keep their existing authorization and confirmation behavior - no new panel assets were added; existing deploy flow for `filament:assets` is unchanged Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #189
130 lines
4.1 KiB
PHP
130 lines
4.1 KiB
PHP
<?php
|
|
|
|
return [
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Default Queue Connection Name
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| 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.
|
|
|
|
|
*/
|
|
|
|
'default' => env('QUEUE_CONNECTION', 'database'),
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Queue Connections
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| 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.
|
|
|
|
|
| Drivers: "sync", "database", "beanstalkd", "sqs", "redis",
|
|
| "deferred", "background", "failover", "null"
|
|
|
|
|
*/
|
|
|
|
'connections' => [
|
|
|
|
'sync' => [
|
|
'driver' => 'sync',
|
|
],
|
|
|
|
'database' => [
|
|
'driver' => 'database',
|
|
'connection' => env('DB_QUEUE_CONNECTION'),
|
|
'table' => env('DB_QUEUE_TABLE', 'jobs'),
|
|
'queue' => env('DB_QUEUE', 'default'),
|
|
'retry_after' => (int) env('DB_QUEUE_RETRY_AFTER', 600),
|
|
'after_commit' => false,
|
|
],
|
|
|
|
'beanstalkd' => [
|
|
'driver' => 'beanstalkd',
|
|
'host' => env('BEANSTALKD_QUEUE_HOST', 'localhost'),
|
|
'queue' => env('BEANSTALKD_QUEUE', 'default'),
|
|
'retry_after' => (int) env('BEANSTALKD_QUEUE_RETRY_AFTER', 600),
|
|
'block_for' => 0,
|
|
'after_commit' => false,
|
|
],
|
|
|
|
'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', 'default'),
|
|
'suffix' => env('SQS_SUFFIX'),
|
|
'region' => env('AWS_DEFAULT_REGION', 'us-east-1'),
|
|
'after_commit' => false,
|
|
],
|
|
|
|
'redis' => [
|
|
'driver' => 'redis',
|
|
'connection' => env('REDIS_QUEUE_CONNECTION', 'default'),
|
|
'queue' => env('REDIS_QUEUE', 'default'),
|
|
'retry_after' => (int) env('REDIS_QUEUE_RETRY_AFTER', 600),
|
|
'block_for' => null,
|
|
'after_commit' => false,
|
|
],
|
|
|
|
'deferred' => [
|
|
'driver' => 'deferred',
|
|
],
|
|
|
|
'background' => [
|
|
'driver' => 'background',
|
|
],
|
|
|
|
'failover' => [
|
|
'driver' => 'failover',
|
|
'connections' => [
|
|
'database',
|
|
'deferred',
|
|
],
|
|
],
|
|
|
|
],
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| 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', 'sqlite'),
|
|
'table' => 'job_batches',
|
|
],
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Failed Queue Jobs
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| These options configure the behavior of failed queue job logging so you
|
|
| 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"
|
|
|
|
|
*/
|
|
|
|
'failed' => [
|
|
'driver' => env('QUEUE_FAILED_DRIVER', 'database-uuids'),
|
|
'database' => env('DB_CONNECTION', 'sqlite'),
|
|
'table' => 'failed_jobs',
|
|
],
|
|
|
|
];
|