- What is Laravel Epilog and what does it do?
- Laravel Epilog is a lightweight package that integrates with Laravel's logging system to persist log entries in a database table, typically called Epilog. Its overview describes a logging channel that stores levels, messages, and context from existing Log:: calls so entries can be queried instead of parsed from files. A secondary blurb also describes model create, update, and delete auditing, so verify the actual API in the repository before adopting it.
- How do I install rap2hpoutre/laravel-epilog in a Laravel app?
- Install it by requiring rap2hpoutre/laravel-epilog with Composer, then publish the package config and migration and run the migration against your database. You then point a Laravel logging channel at the package's driver so Log:: calls are written to the Epilog table. Because the package predates Laravel auto-discovery, expect to register its service provider manually, and confirm the Composer constraints against your Laravel and PHP versions first.
- Which Laravel and PHP versions does Laravel Epilog support?
- The package's last release was in September 2015, so its Composer constraints target that era of Laravel and PHP rather than modern versions. There is no documented official support for Laravel 10, 11, or 12. Run a compatibility spike or inspect composer.json before assuming it will install on your stack.
- How do I configure Laravel to write logs to the Epilog database channel?
- Add a logging channel in config/logging.php that uses the Epilog driver and the package's configuration, then include that channel in your default stack or set it as the default. Existing Log::info, Log::error, and similar calls will then be persisted through Laravel's logging pipeline. Confirm the exact driver name and config keys from the package's published config, because the 2015-era README may not match current Laravel conventions.
- Can Laravel Epilog capture exceptions and Log:: calls automatically?
- Because it plugs into Laravel's logging system, Log:: calls that route through the Epilog channel should be captured along with their level, message, and context. Exception reports can also land in the table if Laravel's exception handler logs them through the same channel or stack. It does not replace Laravel's exception handler or add automatic model auditing unless the package's model-event features are explicitly wired up.
- Is Laravel Epilog maintained and safe for production?
- Treat it as legacy and unmaintained: it has a 2015 release date, low star count, and weak health signals, so there is no active upstream support path. The code footprint is small, which makes a fork tractable, but your team must own compatibility patches, tests, and security review. For production, add retention jobs, PII redaction, access controls, and monitoring rather than relying on defaults.
- What are alternatives to Laravel Epilog for database logging or audit trails?
- For maintained activity trails, evaluate packages such as spatie/laravel-activitylog, or build a small application-owned event table with explicit indexes and retention rules. For log storage, you can also implement a custom Laravel logging channel or use a maintained database or Monolog handler. Choose based on whether you need debugging logs, model activity history, or regulated audit evidence, because Laravel Epilog is not a compliance-grade audit system.
- How do I query and search logs stored by Laravel Epilog?
- Logs are stored in a database table, so you query them through the package's Eloquent model or directly with the query builder. Filter by level, message text, timestamps, and context fields, and add indexes for the columns you search most often. If context is stored as JSON or text, use your database's JSON or full-text features and paginate results to avoid loading large tables.
- Does Laravel Epilog work with Laravel 10, 11, or 12?
- It is unlikely to work out of the box on Laravel 10, 11, or 12 because its 2015-era constraints and manual service-provider registration predate modern Laravel conventions. A fork would likely need namespace updates, provider registration changes, migration review, and tests against your supported PHP and database versions. Run a short non-production spike before committing to direct dependency use.
- What should I consider for PII, retention, and audit compliance with Laravel Epilog?
- Log messages and context can easily contain personal data, tokens, or request payloads, so add redaction before writes and restrict who can query the table. The package does not provide built-in tamper resistance, immutability, or retention policy, so add retention jobs and database access controls yourself. For regulated audit requirements, prefer a maintained package or an in-house design with explicit evidentiary controls.