- Is rikudou/cron-bundle compatible with Laravel?
- No. rikudou/cron-bundle is a Symfony 6 bundle built around Symfony's bundle bootstrapping, service container, and console command registration, none of which exists in a Laravel application. Laravel has no configuration surface to install it into, so it is not a candidate dependency for a Laravel codebase.
- What does rikudou/cron-bundle actually do?
- It parses standard cron expression strings, validates schedules, and computes upcoming or past run times. It is designed to help Symfony applications display human-readable schedules or trigger logic based on cron timing. The portable core idea is evaluating expressions and dispatching only jobs that are due.
- How do I install rikudou/cron-bundle in a Laravel app?
- You cannot install it as a normal Laravel package because it is a Symfony bundle. There is no Laravel service provider or configuration surface to register. The realistic options are using dragonmantank/cron-expression directly, relying on Laravel's native scheduler, or reimplementing the due-job selection logic in a Laravel-native class.
- Can I use rikudou/cron-bundle to schedule Laravel commands?
- Not as shipped. Its scheduling model depends on Symfony console command registration and bundle discovery, so Laravel commands are not discovered or dispatched by it. Laravel already provides this through Illuminate\Console\Scheduling\Schedule. If you need cron parsing only, use dragonmantank/cron-expression, which is already available transitively through Laravel's scheduler.
- What PHP and Symfony versions does rikudou/cron-bundle support?
- The package targets Symfony 6 and PHP 8.x. Versioning to Symfony 6 means it becomes an upgrade liability if you move to Symfony 7, and Symfony 7 support is not identified in the available assessment. For Laravel, its Symfony version constraints are largely irrelevant because the bundle architecture does not fit.
- Is rikudou/cron-bundle production-ready and well maintained?
- The available assessment reports three GitHub stars, zero dependents, a single maintainer, and no evidence of an external review surface or CI. For a scheduler, that support profile is risky because failures are silent and time-based: a job that never fires produces no exception or alert by default. The MIT license and small code surface make a fork possible, but that turns a dependency decision into a maintenance commitment.
- What are the best alternatives to rikudou/cron-bundle for Laravel?
- Laravel's native scheduler is the primary alternative, offering overlap protection, onOneServer support, lifecycle hooks, output logging, and a mature cron expression parser. If you need standalone expression parsing, dragonmantank/cron-expression is the realistic choice and is already present transitively in Laravel. For Symfony projects, the first-party symfony/scheduler component is a better-supported option.
- Does rikudou/cron-bundle handle timezones, DST, and missed runs?
- The provided assessment does not confirm how it handles timezones, DST transitions, or missed runs after downtime. Those points are listed as unresolved and should be verified before any commitment. For Laravel, the native scheduler provides documented timezone options and a support path.
- Does rikudou/cron-bundle provide overlap protection or one-server execution?
- The assessment does not identify overlap protection, lock backing, or one-server execution in this package. That is a critical gap for scheduled jobs because overlapping runs can corrupt data or duplicate processing. Laravel's scheduler provides withoutOverlapping and onOneServer, so adopting this bundle would be a capability loss even outside the framework mismatch.
- Can I fork or vendor rikudou/cron-bundle into a Laravel project?
- Forking is technically viable because the package is MIT licensed and small, but it converts a dependency decision into an ongoing maintenance commitment. The recommended approach is to read the bundle in a throwaway Symfony 6 app, then port only the mechanics you need - expression storage, per-minute due-job filtering, timezone handling, and one lock per job - into a Laravel-native job class. The scope is roughly 150-300 lines, and the bundle should not be introduced as a dependency.