- What is grafite/mission-control-laravel used for?
- It is a Grafite package that adds a configurable control panel to a Laravel application. The panel is intended to give developers one place to inspect runtime state, including at-a-glance health checks, queue and scheduled task visibility, and application log inspection. It is config-driven and ships with publishable Blade views so the panel can be adapted without editing vendor code.
- How do I install grafite/mission-control-laravel?
- Installation is Composer-only: require the package with Composer and then publish its config file and Blade views as described in the package documentation. The package is designed to fit into a Laravel app without a separate build system, but you should still verify the supported Laravel and PHP versions first. Run the install in a scratch application before adding it to an existing project.
- Does grafite/mission-control-laravel support Laravel 10 or Laravel 11?
- That is not confirmed by the available material, and the package's vintage and low recent activity suggest a Laravel 5.8 to 7.x era target. If that is correct, it is likely incompatible with a Laravel 10 or 11 application on PHP 8.2 or newer. Run a half-day scratch install spike to get a definitive answer before estimating any integration work.
- Is Mission Control for Laravel an admin panel or a reporting client?
- The source material is ambiguous. One description frames it as an invasive admin panel that wants to own identity, roles, and the auth surface; another frames it as a thin client that reports app health and queue signals to a self-hosted Mission Control dashboard. Those are very different programs, so resolve which one you are adopting before any security or migration planning.
- Does grafite/mission-control-laravel publish migrations or change my database schema?
- The provided overview only confirms publishable config and Blade views, not migrations. Before installing, check the package's service provider and documentation for published migrations or routes that could collide with your application's schema or URL structure. If migrations are published, plan the exit path and data unwinding before you commit to production use.
- How do I customize the Mission Control dashboard views?
- The package ships with publishable Blade views, so you customize by publishing them into your application and editing the published copies rather than vendor files. Configuration is also publishable and config-driven, which lets you adapt the panel per project. Keep your published views under version control so upgrades are easier to review.
- What can I see in Mission Control for Laravel for queues and scheduled tasks?
- The package advertises queue and scheduled task visibility alongside health and status checks and application log inspection. The intent is to surface runtime state in one dashboard instead of switching between Artisan, log files, and separate tools. The exact detail depends on how the package is installed and configured in your app.
- Is grafite/mission-control-laravel actively maintained?
- The available assessment points to single-maintainer stewardship, very low adoption, no visible SLA, and no CVE feed watching an admin-adjacent surface. Two stars and zero dependents mean there is little downstream usage to surface defects or provide a documentation corpus. Treat support cost as unmeasured and decide up front who owns a fork if upstream stalls.
- Can I use grafite/mission-control-laravel in production?
- Only after a security review and a version pin, because any admin or diagnostic view is a high-value target. Confirm supported Laravel and PHP versions, the complete transitive dependency footprint, whether it publishes migrations or routes, and whether an enabled flag is respected in local and CI environments. The safer default is a time-boxed, non-critical-path evaluation rather than a production dependency unless Mission Control is already a committed vendor choice.
- How do I remove grafite/mission-control-laravel if I stop using it?
- If the package is truly additive, removal is a Composer uninstall plus cleanup of its published config and Blade views. The critical question is whether it published migrations, routes, or auth and role models into your app, because those require a data and schema unwind. Confirm the exit path before adoption so you do not create silent upgrade drag.