Weave Code
Events Log Laravel Laravel Package
avto-dev/events-log-laravel
avto-dev/events-log-laravel is a Laravel package that records application and model events in the database, providing a lightweight audit trail for tracking changes, user actions, and important activity across your application.
Events logging for laravel applications
Frequently asked questions about Events Log Laravel
- How do I install avto-dev/events-log-laravel?
- Install it with Composer using composer require avto-dev/events-log-laravel, then run any migrations the package provides and publish its configuration if needed. Confirm that your application is on Laravel 11 or newer before installing v3.7.0, because that release requires illuminate/* ^11.0. Stage the install first so you can verify the package's database tables and event hooks in your own application.
- Which Laravel versions are supported by avto-dev/events-log-laravel?
- Version 3.7.0 resolves illuminate/* to ^11.0 and adds Laravel 13.x support, so it targets Laravel 11 and newer. Laravel 10 is no longer supported by that release, and applications on 10 should stay on the newest compatible 3.x version, reported as 3.6.x. If Laravel 13 is still pre-release in your environment, treat the 13.x claim as forward-looking and verify compatibility before adopting it.
- Does avto-dev/events-log-laravel work with Laravel 10?
- No, not version 3.7.0. Its illuminate/* constraint is ^11.0, so Composer will refuse to resolve v3.7.0 in a Laravel 10 application and will fall back to the newest compatible 3.x release. For Laravel 10 projects, that means staying on 3.6.x until you complete the framework upgrade.
- What does avto-dev/events-log-laravel log?
- The package records application and model events in the database, giving you a lightweight audit trail for tracking changes, user actions, and important activity. It is aimed at Laravel applications that need event history without a separate auditing service. Review the package's event configuration to choose which application and model events you actually persist.
- How is avto-dev/events-log-laravel different from spatie/laravel-activitylog?
- This package is a Laravel-first events logger that writes application and model events to your database for audit purposes. Spatie's activity log is a broader activity-logging package, so compare them on the events they capture, configuration surface, retention, and how each fits your existing data model. The main practical difference to check first is whether the package's event coverage and database schema match your audit requirements.
- Do I need to run migrations for avto-dev/events-log-laravel?
- The package stores event records in the database, so you should expect it to ship migrations or a publishable schema for its log table. Run the package migrations as part of deployment and confirm the table name and indexes in staging. If the package publishes configuration or migrations, include those publish commands in your deployment notes.
- Will avto-dev/events-log-laravel slow down my Laravel application?
- Every recorded event results in a database write, so logging high-volume model or application events can add overhead. The impact depends on how many events you capture, your database, and whether the log table is indexed and pruned. Benchmark it in staging with production-like traffic and limit logging to the events you actually need for audit purposes.
- Is v3.7.0 a breaking change if I am on Laravel 10?
- Technically yes for Laravel 10 users: it is a minor version bump, but it removes framework support by raising illuminate/* to ^11.0. Composer handles this safely by refusing the install and resolving an older compatible release, so you will not get a broken runtime by accident. Treat the version number as advisory and check the framework constraint before upgrading.
- What PHP version does avto-dev/events-log-laravel require?
- The package's CI image uses PHP 8.5, but the available information does not confirm an explicit php constraint in composer.json. Check the package's composer.json for its declared PHP floor and ensure your runtime image, such as PHP 8.2 or 8.3, satisfies it. That check matters before you adopt v3.7.0 on Laravel 11 or 12.
- How should I test avto-dev/events-log-laravel before using it in production?
- Install it in a staging copy of a real application, run the migrations, and trigger a few model and application events to confirm rows are written correctly. Review whether the package hooks the HTTP kernel, console kernel, or scheduler, since Laravel 11 and newer moved middleware and schedule registration into bootstrap/app.php. Also check composer why-not for version conflicts and verify the package's actual Laravel 13 support if you plan to adopt 13.x.
Weaver
How can I help you explore Laravel packages today?