- How do I install kabbouchi/laravel-ward in a Laravel application?
- Install it with Composer using composer require kabbouchi/laravel-ward, then rely on Laravel package auto-discovery or register the service provider if needed. Publish the package config with php artisan vendor:publish and review the registered dashboard routes before exposing them. Check the package's composer.json constraints against your app's Laravel and PHP versions first.
- Which Laravel and PHP versions does laravel-ward support?
- The last release noted is from 2023-02-20, which predates Laravel 11 and 12. Expect documented constraints around Laravel 9/10 and PHP 8.0/8.1, but verify the actual composer.json before adoption. If your app is newer, you may need a fork with widened constraints and a staging smoke test.
- Is laravel-ward safe to expose in production?
- Not by default. Application logs can contain PII, session identifiers, bearer tokens, stack traces, and database connection strings, so a web dashboard over storage/logs is a data-exfiltration surface. Require authentication, an explicit authorization gate or admin role, and an IP allowlist, and keep it disabled by default in production and internet-facing environments.
- Does laravel-ward include authentication or an authorization gate?
- The package overview describes a service provider that registers routes, views, and config, but it does not document a built-in authorization gate. Plan to wrap the registered routes in your application's existing admin middleware and authorization policy. Inspect the route definitions and middleware hooks in the package source before deploying.
- Can I use laravel-ward with Laravel 11 or Laravel 12?
- That is not indicated by the available release history, which predates Laravel 11 and 12. The practical path is to test on a branch with widened Composer constraints and validate routes, views, log parsing, and authorization in staging. If the smoke test fails or requires extensive changes, reject the package rather than treating it as platform infrastructure.
- What log files does laravel-ward read?
- It is described as a web dashboard over files in storage/logs. Confirm whether it respects your configured log channel and path, including daily or rotated channels and non-default locations, instead of assuming only laravel.log. Validate it against real rotated and oversized log files in staging.
- Is laravel-ward a replacement for Sentry, Datadog, CloudWatch, or Papertrail?
- No. It is a convenience layer for viewing local log files, not a centralized logging or aggregation strategy. Use it for development, staging, or break-glass triage, and keep centralized aggregation for production observability and retention.
- Does laravel-ward work in Docker, Kubernetes, or multi-node deployments?
- It reads logs from the local filesystem of the instance serving the dashboard. In containerized or autoscaled fleets, each pod or server shows only its own local file, which can produce a partial and misleading view. Those environments should ship logs to a central store instead.
- How should I secure laravel-ward routes in a Laravel app?
- Deploy behind your existing admin middleware and an authorization policy, add an IP allowlist, and gate the dashboard behind an environment flag. Roll it out to staging first and review route names, view namespaces, and output escaping for collisions or XSS risk. Treat production access as break-glass triage, not a default-open tool.
- Is laravel-ward actively maintained and easy to remove?
- The available assessment notes 25 stars, a single maintainer, and roughly two-plus years without a release, so maintenance abandonment is a real risk. Adoption is non-invasive because it adds no schema or domain coupling, and removal is effectively a one-line Composer change. If you adopt it, plan for a fork or internal ownership rather than assuming upstream support.