- How do I install mojtabaahn/laravel-web-logs in a Laravel application?
- Install it with Composer using composer require mojtabaahn/laravel-web-logs, then publish the package config if you need to change routes or middleware. Laravel package auto-discovery should register the service provider. Because the package is archived and its last release is from February 2022, prove the install on a branch before adding it to a shared dependency graph. You may need to override PHP or Laravel version constraints or maintain a fork on current stacks.
- Does laravel-web-logs support Laravel 10, Laravel 11, or PHP 8.2+?
- There is no official indication that it supports Laravel 10, Laravel 11, or PHP 8.2+. The last release was in February 2022, which predates those versions. A clean install on a current Laravel stack should be treated as an assumption to prove on a branch, not a fact. Expect to need a fork or dependency constraint override.
- Is it safe to use a web-based Laravel log viewer in production?
- A web-facing log viewer is an information-disclosure risk because logs can contain PII, session identifiers, tokens, internal paths, and third-party payloads. Use this package only with a named auth middleware or gate, not path obscurity, and do a security review before exposure. The archived status adds risk because future advisories will not receive coordinated fixes, so production use is hard to justify when an observability platform already exists. Prefer non-production environments unless you accept ongoing fork ownership.
- How do I protect the laravel-web-logs route with authentication?
- Publish the package config and attach existing Laravel auth middleware or a gate to the viewer route. Confirm the middleware is actually applied in the environment where the route is registered, rather than relying on an obscure URL. Access should be limited to named, authorized users. Treat any default or misconfigured route as an unauthenticated internal-data endpoint.
- Can I change the route URL or middleware for the web log viewer?
- Yes. The package is designed with configurable routes, middleware, and access control, and the evaluation notes publishing the config as part of integration. Change the route path and middleware in the published config, then verify the effective route list. Keep route protection explicit and test it after every config change.
- Which Laravel log formats and channels does this package parse correctly?
- The viewer reads file-based logs from storage/logs through Laravel's filesystem abstraction and renders them in Blade views. It is intended for the default Laravel Monolog-style log format. JSON-formatted logs, custom channels, and multi-line stack traces may be shown partially or misleadingly if the parser does not understand them. Test every channel and formatter you use before relying on it during an incident.
- Does laravel-web-logs work in Docker or containerized Laravel apps?
- It assumes durable, filesystem-backed local logs in the application's storage/logs directory. It does not fit deployments where containers write logs to stdout and ship them to a collector, because the viewer may read an empty or rapidly rotating directory. Confirm your deployment topology before adoption. If logs are centralized, use the observability or log aggregation platform instead.
- How do I search and filter logs in the Laravel web logs UI?
- The package provides a browser UI for viewing, searching, and filtering log files, so you do not need SSH or server access for a quick look. Search and filtering do not remove the need to check performance and memory behavior on large files. Logs are often largest after an incident, exactly when you need them. Test the viewer against realistic log sizes and your retention and rotation policy.
- Is mojtabaahn/laravel-web-logs still maintained, and what happens if it breaks?
- No. The package is archived, and the last release was in February 2022, so there is no vendor actively absorbing Laravel and PHP compatibility drift. If you adopt it, your team owns any fork, patches, and security remediation indefinitely. Define an owner and a retirement trigger before adoption. For new work, prefer an actively maintained Laravel log viewer or your existing observability stack.
- What are the alternatives to laravel-web-logs for viewing Laravel logs?
- Consider actively maintained Laravel log viewer packages and your existing log aggregation or observability platform. The best alternative depends on whether logs are local files or shipped to a collector and whether the environment is production. If you only need occasional non-production peeks, a small maintained viewer may be enough. If you need production troubleshooting, centralized logging is the safer default.