Web Command Bundle Laravel Package

Product Decisions This Supports

• Internal Developer Tools (IDT) Initiative: Accelerate backend operations (e.g., cron jobs, data migrations, reports) without CLI access, reducing dependency on DevOps for manual executions.
• Self-Service Analytics/ETL: Enable non-technical stakeholders (e.g., analysts, marketers) to trigger data pipelines via a UI dashboard (e.g., EasyAdmin) with proper access controls.
• Build vs. Buy: Avoid reinventing a secure, scalable command-execution API for Laravel/Symfony apps. Justifies investment in a maintained package over custom development.
• Roadmap Priorities:
  • Phase 1: Replace ad-hoc CLI scripts with API-driven workflows (e.g., "Run php artisan queue:work via browser").
  • Phase 2: Integrate with CI/CD for post-deploy validation (e.g., "Trigger php artisan migrate after merge").
  • Phase 3: Extend to multi-tenant SaaS for tenant-specific command execution (e.g., "Run php artisan tenant:backup for Acme Corp").
• Use Cases:
  • Operational: Schedule one-off tasks (e.g., "Generate monthly report now").
  • Debugging: Execute commands in dev/staging with timeouts (e.g., "Test php artisan optimize without blocking").
  • Compliance: Audit command history for security/review (via EasyAdmin).

When to Consider This Package

• Adopt if:

  • Your Laravel/Symfony app needs CLI functionality exposed as an API (e.g., for webhooks, dashboards, or mobile apps).
  • You require asynchronous execution (via Messenger) to avoid timeouts for long-running commands (e.g., data imports).
  • Your team uses EasyAdmin or needs a built-in dashboard for command management/history.
  • You prioritize security (e.g., voters for command access control) and configurability (memory/time limits per command).
  • You’re already using Symfony Messenger or want to adopt it for async workflows.

• Look elsewhere if:

  • You need Laravel-specific features (this is Symfony-focused; consider laravel-webcommands instead).
  • Your commands require GUI input (e.g., interactive prompts)—this is API-only.
  • You lack Symfony components (e.g., Messenger, EasyAdmin) and don’t want to add dependencies.
  • You need multi-server orchestration (e.g., Kubernetes jobs)—this is single-instance.
  • The package’s maturity (0 stars, unproven) is a risk; prefer spatie/laravel-webcommands (10K+ stars) for Laravel.

How to Pitch It (Stakeholders)

For Executives:

"This package lets us turn manual CLI tasks—like running reports or migrations—into self-service tools accessible via a web interface. For example, our marketing team could trigger a customer-segmentation job on demand instead of waiting for DevOps. It also adds auditability (who ran what, when) and scales async tasks without blocking users. The cost? Minimal—just a Composer install and 1–2 hours of config. ROI comes from reduced ops overhead and faster iteration."

Ask:

• "Would you prioritize reducing dependency on CLI access for non-dev teams?"
• "Is async execution a blocker for any of our long-running processes?"

For Engineering:

*"This bundle gives us a batteries-included way to expose Symfony console commands via REST API, with:

• Async support: Offload heavy commands to Messenger (no timeouts).
• Security: Voters to restrict access (e.g., only admins run php artisan down).
• Observability: EasyAdmin dashboard for command history/job status.
• Flexibility: Configure memory/time limits per command (e.g., php artisan optimize gets 2GB RAM).

Tradeoffs:

• Symfony-first (but works with Laravel via Symfony components).
• Unproven (0 stars), but MIT-licensed and actively maintained (recent 2026 release).
• Alternative: spatie/laravel-webcommands if you’re Laravel-only.

Proposal:

1. Pilot: Expose 3 high-impact commands (e.g., queue:work, migrate, report:generate) via API.
2. Integrate: Add EasyAdmin for non-dev visibility.
3. Scale: Extend to async workflows (e.g., post-deploy validation).

Next Steps:

• Confirm Symfony/Messenger compatibility with our stack.
• Review spatie/laravel-webcommands as a fallback.
• Allocate 1 sprint to prototype and benchmark against custom solution."*

Visual Aid for Pitch:

Before: DevOps runs `php artisan report:generate` manually → Slow, no audit trail.
After: Marketing clicks "Generate Report" in EasyAdmin → Async job runs, email alerts on completion.