Filament Artisan Laravel Package

Product Decisions This Supports

• Developer Experience (DX) Enhancement: Accelerates backend operations by exposing Artisan commands directly in the Filament admin panel, reducing reliance on CLI access and improving workflow efficiency for non-technical stakeholders.
• Internal Tooling Roadmap: Ideal for teams building admin dashboards where CLI access is limited (e.g., shared hosting, PaaS environments) or where developers need to delegate command execution to admins (e.g., cache clearing, migrations, queue processing).
• Build vs. Buy: Buy—avoids reinventing a UI for Artisan commands, saving dev time. Justify with cost-benefit analysis (e.g., "This reduces onboarding time for non-dev admins by X hours").
• Use Cases:
  • DevOps/Admins: Run commands like migrate, cache:clear, or queue:work without SSH.
  • Feature Flags: Toggle commands (e.g., filament-artisan:flush) for specific roles.
  • Auditability: Log command executions via Filament’s activity logs.
  • Multi-tenant SaaS: Restrict commands to specific tenants via Filament’s policies.

When to Consider This Package

• Adopt if:

  • Your team uses FilamentPHP and needs a low-code way to expose Artisan commands to non-developers.
  • You’re in a shared environment (e.g., Heroku, Forge) where CLI access is restricted.
  • You want to reduce context-switching (e.g., devs no longer need to explain CLI commands to admins).
  • Your roadmap includes self-service operations (e.g., "Admins can reset caches without tickets").

• Look elsewhere if:

  • You need advanced command customization (e.g., dynamic arguments, pre/post hooks)—consider building a custom Filament resource.
  • Your team already has a CLI-first culture and no need for UI access.
  • You require real-time command monitoring (e.g., progress bars, timeouts)—this package focuses on simplicity.
  • You’re using Laravel Octane or Horizon (this package doesn’t integrate with those).

How to Pitch It (Stakeholders)

For Executives:

"This package lets non-technical admins run critical backend tasks (like database migrations or cache flushes) directly from the Filament dashboard—no CLI knowledge required. It cuts down on developer tickets for routine operations, speeds up deployments, and reduces downtime. For example, our support team could clear failed queue jobs in seconds instead of waiting for devs. The MIT license and minimal setup make it a no-brainer for our Filament-based admin panels."

Ask: "Would you prioritize reducing operational friction for admins, even if it’s a small team?"

For Engineering:

*"This is a 5-minute plugin that solves a recurring pain point: exposing Artisan commands to Filament users. Key benefits:

• Zero dev overhead: Just install, register in AdminPanelProvider, and go.
• Security: Commands are restricted to local environments by default (configurable).
• Extensible: You can whitelist/blacklist commands via Filament’s policies.
• Audit trail: All executions are logged in Filament’s activity feed.

Trade-offs:

• Not for complex workflows (e.g., multi-step commands).
• Output is basic (no syntax highlighting, but sufficient for most use cases).

Proposal: Let’s pilot this for our staging environment first—target admins can run migrate:fresh and queue:flush without SSH. If it saves 2+ hours/month, we scale it."*

Ask: "Does this align with our goal to reduce manual CLI dependency in Filament?"