remco/Atomcms-edit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: update doctrine/dbal to v4, activitylog to v5, sluggable to v4, roadrunner-http to v4

Browse Source
This commit is contained in:
root
2026-05-23 17:20:57 +02:00
parent 2d5f018ff1
commit 81839c7202
6 changed files with 198 additions and 256 deletions
Download Patch File Download Diff File Expand all files Collapse all files
config/activitylog.php
+31 -14
View File
@@ -1,7 +1,7 @@
<?php
declare(strict_types=1);
use Spatie\Activitylog\Actions\CleanActivityLogAction;
use Spatie\Activitylog\Actions\LogActivityAction;
use Spatie\Activitylog\Models\Activity;
return [
@@ -9,13 +9,13 @@ return [
/*
* If set to false, no activities will be saved to the database.
*/
'enabled' => env('ACTIVITY_LOGGER_ENABLED', true),
'enabled' => env('ACTIVITYLOG_ENABLED', true),
/*
* When the clean-command is executed, all recording activities older than
* When the clean command is executed, all recording activities older than
* the number of days specified here will be deleted.
*/
'delete_records_older_than_days' => 365,
'clean_after_days' => 365,
/*
* If no log name is passed to the activity() helper
@@ -30,9 +30,10 @@ return [
'default_auth_driver' => null,
/*
* If set to true, the subject returns soft deleted models.
* If set to true, the subject relationship on activities
* will include soft deleted models.
*/
'subject_returns_soft_deleted_models' => false,
'include_soft_deleted_subjects' => false,
/*
* This model will be used to log activity.
@@ -42,15 +43,31 @@ return [
'activity_model' => Activity::class,
/*
* This is the name of the table that will be created by the migration and
* used by the Activity model shipped with this package.
* These attributes will be excluded from logging for all models.
* Model-specific exclusions via logExcept() are merged with these.
*/
'table_name' => 'activity_log',
'default_except_attributes' => [],
/*
* This is the database connection that will be used by the migration and
* the Activity model shipped with this package. In case it's not set
* Laravel's database.default will be used instead.
* When enabled, activities are buffered in memory and inserted in a
* single bulk query after the response has been sent to the client.
* This can significantly reduce the number of database queries when
* many activities are logged during a single request.
*
* Only enable this if your application logs a high volume of activities
* per request. Buffered activities will not have an ID until the
* buffer is flushed.
*/
'database_connection' => env('ACTIVITY_LOGGER_DB_CONNECTION'),
'buffer' => [
'enabled' => env('ACTIVITYLOG_BUFFER_ENABLED', false),
],
/*
* These action classes can be overridden to customize how activities
* are logged and cleaned. Your custom classes must extend the originals.
*/
'actions' => [
'log_activity' => LogActivityAction::class,
'clean_log' => CleanActivityLogAction::class,
],
];