Weave Code
Cron Bundle Laravel Package
lingoda/cron-bundle
Lingoda Cron Bundle adds cron job scheduling to Symfony applications, letting you define recurring tasks and run console commands on configured schedules from a single, centralized bundle.
Lingoda cron bundle
Frequently asked questions about Cron Bundle
- Can I use lingoda/cron-bundle in a Laravel application?
- Not idiomatically. It is a Symfony bundle and provides no Laravel ServiceProvider, facade, or package auto-discovery, so Composer may install it but Laravel will not wire it up like a native package. You would need a custom bridge or to invoke its scheduling logic manually. For most Laravel apps, the built-in Schedule component is the simpler path.
- How do I install lingoda/cron-bundle with Composer?
- Install it as a Composer dependency with composer require lingoda/cron-bundle in a Symfony or plain PHP application. You then register the bundle in your application kernel or bundle configuration and define jobs through the bundle configuration layer. In Laravel there is no auto-discovery, so manual bootstrapping would be required. Check the repository README for the exact registration and configuration syntax for your Symfony version.
- Does lingoda/cron-bundle support Laravel's scheduler or auto-discovery?
- No. Laravel auto-discovery relies on a package service provider, and this project is a Symfony bundle with none of that Laravel-specific metadata. It will not register commands, configuration, or schedules inside a Laravel app automatically. You can still call it from Laravel code, but you are responsible for bootstrapping, configuration, and execution.
- What bug was fixed in lingoda/cron-bundle 2.3.1?
- Version 2.3.1 prevents new scheduled jobs from firing immediately on deploy. Before the fix, introducing a new schedule could cause the job to run as soon as the application restarted or the new definition was picked up. That is a deploy-lifecycle bug that can create duplicate side effects such as invoices, notifications, or billing retries. The patch release addresses the first-run baseline behavior.
- Which versions of lingoda/cron-bundle are affected by jobs firing immediately on deploy?
- Versions 2.3.0 and below are affected according to the release note for 2.3.1. If you are running any earlier tag, new scheduled jobs may fire immediately when they are first introduced. Upgrade to 2.3.1 or later if you use the package in production. Treat any pre-2.3.1 deployment as having potential duplicate-run exposure.
- How does lingoda/cron-bundle store job state and next-run times?
- The fix implies the bundle persists per-job state and computes next-run times from a stored baseline. That state store could be a database table, cache, or filesystem depending on configuration, but the package owns runtime scheduling and job identity. In a multi-instance deployment, that store becomes a shared dependency you must provision, back up, and keep consistent. Verify the exact store and locking behavior in the package source before relying on it.
- What are the alternatives to lingoda/cron-bundle for Laravel scheduling?
- Laravel's native Schedule component with schedule:run or schedule:work is the first-party alternative and already uses cron-expression evaluation. dragonmantank/cron-expression is the common library for parsing cron expressions if you need that piece alone. symfony/scheduler is the closer Symfony-native analogue if you are working outside Laravel. For Laravel shops, lingoda/cron-bundle adds bridge cost without replacing native behavior.
- Is lingoda/cron-bundle actively maintained and production-ready?
- Maintenance is unproven but non-zero. The 2.3.1 patch is a positive signal because it fixes a deploy-lifecycle edge case, which suggests real production usage and a maintainer who ships. However, the project has a single maintainer, very low star count, and no dependents, so bus factor and long-term support are real concerns. Validate tag provenance and changelog continuity before trusting the release history.
- How does catch-up scheduling in lingoda/cron-bundle differ from Laravel Schedule?
- A stored-last-run model implies the bundle may compute and fire missed runs after downtime, whereas Laravel's Schedule evaluates the current minute and silently skips missed windows. That is a genuine behavioral divergence and the clearest reason to consider the package over native scheduling. Whether backfill is desirable is a product decision, not a technical one. If you do not need missed-run recovery, you are paying integration cost for behavior you deliberately avoided.
- Can I bridge lingoda/cron-bundle into Laravel, and how much effort does it take?
- A bridge is feasible but not trivial. Expect roughly two to five engineer-days for a spike, plus additional work to understand and provision the package's state store. You would need to bootstrap the Symfony bundle or call its scheduling internals from Laravel, and you would not get native Laravel command or event integration. Only justify the spike if you have a concrete business requirement for missed-run backfill.
Weaver
How can I help you explore Laravel packages today?