- Is psf1/cron-bundle compatible with Laravel?
- psf1/cron-bundle is presented as a Symfony-style CronBundle, not a native Laravel package. The available metadata shows no Laravel service provider, Eloquent persistence, or Laravel-specific integration, so it is not a drop-in fit for a Laravel application. Treat it as reference material unless you build a compatibility layer or reimplement the scheduling logic with Laravel's scheduler.
- How do I install psf1/cron-bundle?
- The normal Composer install would be composer require psf1/cron-bundle, followed by registering the bundle in a Symfony application. For Laravel, package discovery should not be presumed because the package is Symfony-oriented and the metadata does not confirm Laravel auto-discovery. Verify the declared dependency constraints before adding it to an existing project.
- What PHP and Symfony versions does psf1/cron-bundle support?
- The repository metadata does not confirm supported PHP or Symfony version ranges. The last release noted in the evaluation is dated February 2022, which likely predates Symfony 6.1+ and 7.x and may target PHP 7.4 or 8.0. Run a Composer dependency-resolution spike against your exact runtime before committing to it.
- Does psf1/cron-bundle require Doctrine for schedule storage?
- The evaluation notes that Symfony bundles of this type often rely on Doctrine ORM entities and migrations, but Doctrine persistence is not confirmed from the repository metadata alone. If psf1/cron-bundle does use Doctrine, a Laravel application would inherit a Doctrine dependency or need its persistence layer rewritten for Eloquent. Confirm this in the source or with the maintainer before planning adoption.
- How are scheduled jobs triggered in psf1/cron-bundle?
- The overview describes dynamic cron management where recurring jobs are checked for due status and then dispatched. Architecturally that implies a single tick entry point, likely one system cron line calling a console command, plus a dispatcher and some execution record. The repository metadata does not confirm whether an HTTP trigger route also exists, so review that before exposing it.
- Can psf1/cron-bundle execute both HTTP requests and console commands?
- The package description and evaluation indicate it can dispatch HTTP requests or console commands from a data-driven schedule store. That makes it useful for cron-style jobs that call endpoints or run CLI tasks. Because it can execute commands, security review of authentication, authorization, and input validation is essential before production use.
- Does psf1/cron-bundle prevent overlapping cron jobs across multiple servers?
- The evaluation flags overlapping ticks, duplicate dispatch across app nodes, and DST or timezone handling as classic scheduler risks, and there is no evidence in the metadata that psf1/cron-bundle addresses them. Multi-node deployments would need locking, mutex, or single-flight guarantees before trusting the scheduler. Test concurrency behavior explicitly if you proceed.
- Is psf1/cron-bundle actively maintained and clearly licensed?
- The evaluation reports zero stars, zero dependents, and a release frozen at February 2022, which suggests low ecosystem activity and bus factor 1. It also states that the license, tests, CI, and static analysis are not confirmed from repository metadata. Confirm maintenance status and licensing before adding it to a dependency graph.
- How does psf1/cron-bundle compare with Laravel's scheduler?
- Laravel already provides a Schedule facade, schedule:run invoked once per minute from cron, and withoutOverlapping() for common scheduling needs. psf1/cron-bundle may offer a data-driven cron registry, but it is not a demonstrated Laravel-native alternative. For Laravel teams, reading its design and implementing the equivalent with Laravel's scheduler is usually lower risk.
- What should I test before using psf1/cron-bundle in production?
- Verify license, PHP and Symfony version constraints, Doctrine persistence assumptions, and how the tick entry point is secured. Exercise command execution, HTTP dispatch, failure paths, logging, retries, timezone handling, and overlapping-run behavior under concurrency. Also check the schedule table's retention and growth policy, since the metadata does not confirm it.