Weave Code
Task Bundle Laravel Package
glooby/task-bundle
Glooby Task Bundle is a PHP bundle for defining, organizing, and running background tasks, with a lightweight task registry, console/worker integration, and extensible handlers for scheduling recurring or one-off work in Symfony applications.
glooby/task-bundle is a lightweight Symfony bundle for turning application work into discrete, reusable tasks. It gives you a clear structure for defining task logic, wiring dependencies through the service container, and invoking tasks from application code or console commands—keeping controllers and commands focused.
- Define tasks as dedicated, container-managed services
- Trigger tasks from app code or Symfony console
- Reuse task classes for scheduled or ad-hoc work
- Minimal setup with standard bundle registration
- Easy to extend for custom task workflows
Frequently asked questions about Task Bundle
- Is glooby/task-bundle compatible with Laravel?
- No. glooby/task-bundle is a Symfony bundle, not a Laravel package, so Laravel's service providers, Artisan commands, and config files do not read its bundle registration or service definitions. Composer may install it, but nothing will boot in a Laravel kernel. Treat it as a reference implementation rather than a drop-in dependency.
- Can I install glooby/task-bundle with Composer in a Laravel project?
- Composer may resolve and install it, but the package's Symfony constraints and 2019-era PHP requirements will likely conflict with Laravel 10 or 11, which use PHP 8.1+ and Symfony 6 or 7 components. Even if installation succeeds, there is no Laravel service provider or Artisan entrypoint to activate it. Do not add it as a production dependency without a porting plan.
- Which Laravel versions does glooby/task-bundle support?
- None officially. It is a Symfony bundle last released in 2019, so its PHP and Symfony constraints are likely aimed at PHP 7.x and Symfony 3 or 4, not Laravel 10 or 11. There is no documented Laravel integration path.
- What is glooby/task-bundle used for?
- It defines, persists, and manages tasks as Doctrine entities and provides Symfony console commands for executing queued work and tracking status and progress. It is a foundation for background jobs and scheduling workflows in Symfony applications. Those concepts can be studied, but the bundle is not designed for Laravel.
- How do I use glooby/task-bundle scheduling logic in Laravel?
- Run a timeboxed feasibility spike to audit how tightly the scheduling core is coupled to Symfony's container and event dispatcher. If the domain logic is separable, extract it into a framework-agnostic package and wrap it in a Laravel service provider with an Artisan command. Do not try to boot the Symfony bundle inside Laravel. Expect one to three sprints for a shim plus hardening before product value.
- Is glooby/task-bundle still maintained?
- No. The last release was 2019-10-18, making it roughly seven years stale, with about 30 stars, zero dependents, and effectively a single maintainer. There is no successor or active community support channel. That staleness is a major adoption risk.
- What are the security risks of using glooby/task-bundle?
- The MIT license is permissive, but an unmaintained dependency means transitive CVE patching is entirely your responsibility. Composer resolution may pin old transitive packages to vulnerable versions. With no downstream users or bug reports, you also have little informal validation of security issues.
- What are the best Laravel alternatives to glooby/task-bundle?
- Laravel's native scheduler, queue, and Horizon cover most cron-style recurring tasks and persisted task state. For schedule monitoring, consider spatie/laravel-schedule-monitor; for cron parsing, dragonmantank/cron-expression; for durable orchestration, evaluate Temporal or Flow. For most Laravel use cases, native tools already cover 80% or more of the requirement.
- Does glooby/task-bundle work with Symfony 6 or Symfony 7?
- Probably not without a fork. Its 2019 release likely constrains Symfony to ^3 or ^4, while Symfony 6 and 7 require newer PHP and component versions. You would need to verify and upgrade the bundle yourself. There is no maintained release for modern Symfony.
- Should I use glooby/task-bundle in a production Laravel application?
- Only after a parity analysis shows a material gap that Laravel Scheduler, Queue, and Horizon cannot close. Pilot any extracted logic on a single non-critical scheduled job and compare observability, failure handling, and retry behavior against native tooling. Assign an owner and a 24-month maintenance budget before proceeding. If the delta is thin, build native instead.
Weaver
How can I help you explore Laravel packages today?