- Can I use goksagun/scheduler-bundle in a Laravel application?
- It is a Symfony bundle built around Symfony's DI container and compiler passes, not a Laravel package with a service provider or facade. You could only use it in Laravel behind a custom adapter or as vendored code, and that would be a substitution for Illuminate\Console\Scheduling\Schedule rather than an add-on. Given Laravel already ships a framework-owned scheduler, direct adoption is not recommended.
- How do I install goksagun/scheduler-bundle?
- Installation would be via Composer using goksagun/scheduler-bundle, then registering the bundle in a Symfony kernel rather than Laravel's config/app.php providers array. There is no publishable Laravel config or service provider in the package. For Laravel, you would need to write your own integration layer, so installation alone does not make it usable.
- What Laravel versions does goksagun/scheduler-bundle support?
- The package is a Symfony bundle and does not declare Laravel version support. Its Composer constraints target Symfony components, which Laravel also pins, so compatibility depends on whether those constraint sets intersect cleanly with your Laravel version. Treat any Laravel use as unsupported and verify composer.json constraints before considering it.
- How does SchedulerBundle compare to Laravel's built-in scheduler?
- Laravel's Illuminate\Console\Scheduling\Schedule already provides cron parsing, withoutOverlapping, onOneServer, runInBackground, success and failure hooks, and schedule:list and schedule:test commands. SchedulerBundle offers a Symfony-native way to define recurring jobs in configuration, but it does not replace those Laravel-specific features out of the box. For a Laravel codebase, the built-in scheduler is the lower-risk default.
- Does SchedulerBundle support cron expressions and timezones?
- The package is designed for defining recurring scheduled tasks, so cron-style timing is part of its core purpose, but the provided context does not confirm its timezone and DST handling. Laravel's scheduler has documented timezone support and DST edge-case handling that you would need to match before replacing it. Audit the source and test DST transitions before relying on it.
- How do I configure scheduled tasks with SchedulerBundle?
- In Symfony you would register the bundle and define schedules through its configuration tree and dependency-injection extension. There is no Laravel-style config/scheduler.php or service provider to publish. In Laravel you would have to build a wrapper that translates your application's schedule definitions into whatever API the bundle exposes.
- Does SchedulerBundle prevent overlapping task runs on multiple servers?
- The context does not confirm overlap prevention, distributed locking, or cross-process coordination. Laravel's scheduler provides withoutOverlapping and onOneServer backed by cache locks, which are critical for multi-node deployments. You must verify the bundle's locking backend, such as Redis, file locks, or database advisory locks, before trusting it in production.
- Is SchedulerBundle actively maintained and production-ready?
- The package has very low ecosystem signal, with 7 stars and 0 dependents, and no visible release cadence or CI matrix in the provided assessment. A single-maintainer scheduler in the execution path is load-bearing infrastructure with limited support. Treat it as unproven and not production-ready for a Laravel application without a source audit.
- What are alternatives to SchedulerBundle for Laravel scheduling?
- The primary alternative is Laravel's built-in scheduler, which is framework-owned and already integrates with cache locks, the event dispatcher, and artisan commands. If you need features Laravel lacks, such as dependency ordering between tasks, look at dedicated Laravel packages or a small internal abstraction rather than a Symfony bundle. Server crontabs remain an option but move logic outside the application.
- Can I test SchedulerBundle tasks in CI without running cron?
- The provided context does not confirm a schedule:list or schedule:test equivalent for SchedulerBundle, so CI testing would depend on how the bundle exposes task registration. Laravel's scheduler includes schedule:test and schedule:list specifically for inspecting and triggering tasks without waiting for cron. Without a documented test path, you would need to write integration tests against the bundle's registry or adapter.