Weave Code
Cron Manager Laravel Package
norvutec/cron-manager
norvutec/cron-manager is a Laravel package for managing scheduled tasks in one place: define and run cron jobs, track execution status and history, and keep an eye on failing tasks without digging through server crontabs.
Bundle for managing cronjobs in a symfony project
Frequently asked questions about Cron Manager
- Does norvutec/cron-manager work with Laravel, or is it Symfony-only?
- The package description calls it a bundle for managing cron jobs in a Symfony project, while evaluations of the 7.x line treat it as a Laravel scheduled-task manager. That ambiguity matters, so check composer.json and the source for Illuminate\Console\Scheduling\Schedule integration before committing. If the 7.x code only binds to Symfony's console events, it will not slot into a Laravel app without an adapter. Confirm the target framework first; it is the cheapest question to answer and the most expensive to get wrong.
- How do I install norvutec/cron-manager with Composer?
- Install with composer require norvutec/cron-manager:^7.0.1 so you pin the patch line rather than the whole 7.x range. Read the package's service provider registration and migration steps before running it against a real application database. Adopt it on a non-critical schedule first and keep the native scheduler running in parallel until you have observed a few successful runs. There is no changelog prose in the 7.0.1 release, so verify the install steps against the repository rather than assuming a standard Laravel package layout.
- Does norvutec/cron-manager wrap Laravel's scheduler or replace it?
- The release material does not state this, and it is the decisive architectural question for adoption. A wrapper adds DB-backed schedule definitions, run history, or overlap control on top of the framework scheduler and is additive and cheap. A replacement introduces a second scheduling authority, duplicates cron semantics outside the framework's guarantees, and means Laravel upgrades stop improving your scheduling behaviour. Read the source for direct use of the Schedule facade or of Illuminate scheduling events before deciding.
- Is norvutec/cron-manager 7.0.1 a safe upgrade?
- The 7.0.1 release body contains only a GitHub compare link with no changelog, no declared breaking change, and no declared security fix. A patch release can still alter runtime behaviour, dependency constraints, or migrations, so read the 7.0.0 to 7.0.1 compare diff before merging. Treat the version number as a signal of intent, not a proxy for safe. Confidence is low-to-moderate until that diff is reviewed.
- What broke in norvutec/cron-manager 7.0.0 compared to 6.x?
- The 7.0.0 release, which carries the actual breaking-change risk of a major version, is not covered by the available review material. No upgrade guide is present in the release notes, so the breaking changes are unknown rather than nonexistent. Expect a short tail of 7.0.x fixes, since a patch on a recently shipped major usually signals stabilisation work. Budget for two to three upgrade cycles in the first two quarters and read the repository changelog before planning the migration.
- Which PHP and Laravel versions does norvutec/cron-manager support?
- The supported matrix is not documented in the release material reviewed. Check the composer.json require constraints and the CI matrix in the repository to confirm PHP versions, Laravel versions, and whether Laravel 10 being end-of-life constrains you. If your application is on Laravel 11 or later, verify that the package works with the routes/console.php scheduling style as well as the older Console Kernel. Pin the constraint that matches your platform and test the matrix in a staging environment.
- Does norvutec/cron-manager handle overlapping jobs and multiple app servers safely?
- Overlap control and distribution semantics are not described in the release notes, and they are the difference between a safe scheduler and duplicated work. Look for withoutOverlapping or mutex equivalents and check whether the lock store is a shared cache or database rather than a local file. File-based locks on one host are not safe when several app servers run the same cron entry. Verify exit-code and timeout behaviour on your multi-server topology before trusting it with anything that must run exactly once.
- Where does norvutec/cron-manager store schedules and run history, and will it bloat my database?
- The package appears to keep schedule definitions and execution history in package-owned tables, but the data model and retention policy are not documented in the release notes. Inspect the migrations for log tables, indexes, and any pruning command or configurable retention window. Unbounded run history on a busy schedule will grow the primary database, so plan a retention job from day one. Also note the lock-in cost: if definitions live only in package tables, reverting to the native scheduler later is a data migration rather than a config change.
- Is norvutec/cron-manager secure if it ships a UI for editing cron schedules?
- Editing cron entries is effectively remote code execution, so this needs an explicit answer from the source, not an assumption. Check whether the package registers routes, what middleware and authorization guard them, and whether changes are written to an audit trail. If a UI exists, restrict it to trusted operators, disable it in production where it is not needed, and review the CSRF and policy checks. Absence of documentation on authorization is a finding in itself.
- How do I monitor failing jobs with norvutec/cron-manager, and how do I exit if it is abandoned?
- Scheduling bugs fail quietly, so confirm the package captures exit codes, stores run history, and can hook into your existing monitoring rather than relying on its own dashboard alone. Verify whether failure alerting exists or whether you must poll the history table. Because this is a small-vendor package sitting in the scheduling path of your application, also check maintainer count, release cadence over twelve months, and whether the licence permits an internal fork. Ask up front how definitions export back to native scheduler config, since that export path is your rollback plan.
Weaver
How can I help you explore Laravel packages today?