Weave Code
Scheduler Bundle Laravel Package
aboutcoders/scheduler-bundle
Symfony bundle for defining recurring schedules and dispatching notifications via the Symfony EventDispatcher. Designed to be integrated into your app by implementing your own schedule entities, with docs for installation, configuration, and custom schedule types.
At a glance
Frequently asked questions about Scheduler Bundle
- Can I use AbcSchedulerBundle directly in a Laravel project without Symfony?
- No, this bundle is Symfony-specific and requires integration via a compatibility layer (e.g., Symfony Bridge for Laravel) or a microservice approach. Laravel’s native `Schedule` facade or `spatie/laravel-schedule` may be simpler alternatives for pure Laravel projects.
- How do I define recurring schedules with this bundle?
- You must implement custom schedule entities (e.g., Doctrine models) to define schedules. The bundle provides infrastructure for recurring events and dispatches Symfony events when schedules trigger. Refer to the [AbcJobBundle](https://github.com/aboutcoders/job-bundle) for a real-world example.
- Does this bundle support Laravel’s native queues or jobs?
- No, it dispatches Symfony events, which would need to be mapped to Laravel jobs or queues (e.g., via event listeners). You’d need to bridge Symfony’s EventDispatcher to Laravel’s `Event` facade or queue system manually.
- What Laravel versions are compatible with AbcSchedulerBundle?
- The bundle itself doesn’t support Laravel directly, but if integrated via Symfony Bridge or a microservice, compatibility depends on the bridge’s Laravel version support. Test thoroughly, as Symfony components may not align perfectly with Laravel’s ecosystem.
- How do I associate schedules with Laravel Eloquent models?
- You’d need to create custom Doctrine entities (not Eloquent) to represent schedules, then link them to your Eloquent models via foreign keys or relationships. This requires mapping Laravel migrations to Doctrine schemas, which may introduce complexity.
- Are there performance concerns with custom schedule entities?
- Yes, custom entities add database overhead compared to Laravel’s lightweight `Schedule` facade. If your app relies on high-frequency schedules, test performance under load, especially if using Doctrine ORM alongside Eloquent.
- Can I use this bundle for user-specific recurring tasks (e.g., notifications)?
- Yes, but you’ll need to implement logic to associate schedules with user entities. The bundle’s flexibility allows for custom schedule types (e.g., per-user cron jobs), but this requires additional development effort compared to Laravel’s built-in solutions.
- What’s the best way to test this bundle in a Laravel project?
- Start with a proof-of-concept using Docker to isolate Symfony and Laravel environments. Test event dispatching between them, then gradually integrate critical schedules. Use Laravel’s testing tools to verify Symfony events trigger expected Laravel jobs/listeners.
- Are there alternatives to AbcSchedulerBundle for Laravel?
- Yes, consider `spatie/laravel-schedule` for native Laravel support, or Laravel’s built-in `Schedule` facade for simple cron-like tasks. If you need Symfony’s EventDispatcher, evaluate the `symfony/bridge` package for Laravel integration risks.
- How do I handle time zones or daylight saving adjustments with this bundle?
- The bundle relies on Symfony’s `DateTime` handling, which supports time zones. Configure your custom schedule entities to store time zones explicitly, then ensure Symfony’s time zone settings align with Laravel’s (e.g., via `config/app.php`).
Weaver
How can I help you explore Laravel packages today?