Weave Code
Native Cron Laravel Package
mintware-de/native-cron
A lightweight Laravel/PHP package for integrating native cron jobs into your application. It simplifies scheduling recurring tasks and managing cron entries, so you can run background work without relying solely on framework-specific scheduling. Simple to install and use.
mintware-de/native-cron lets Laravel applications register their scheduled tasks directly with the operating system's native cron daemon instead of relying on schedule:run being invoked every minute. It bridges Laravel's scheduler with real system crontab entries, giving you precise, per-task execution times.
- Installs and syncs system crontab entries from your Laravel schedule
- Supports per-task intervals without a every-minute master job
- Works with the standard
Kernel::schedule()definition - Reduces overhead by letting cron trigger tasks directly
Frequently asked questions about Native Cron
- What is mintware-de/native-cron used for?
- It is a PHP package for managing native unix cron jobs from Laravel applications. You can define schedules and install or remove real crontab entries without manually editing crontab files. This keeps the reliability of the system cron daemon while letting your Laravel app manage job lifecycle.
- How do I install native-cron in a Laravel project?
- Install it through Composer with composer require mintware-de/native-cron. After installation, follow the package README for any service provider registration or configuration steps. Because repository details are not provided here, check the package composer.json for exact Laravel and PHP version constraints.
- Does native-cron replace Laravel's task scheduler?
- No, it addresses a different layer. Laravel's scheduler typically relies on one cron entry that runs schedule:run, while native-cron manages individual native crontab jobs directly. You can use native-cron alongside the Laravel scheduler if you need real system cron entries for specific tasks.
- Which Laravel and PHP versions does native-cron support?
- The supplied context does not list exact version constraints. Check the package composer.json on Packagist for its required PHP version and Laravel framework compatibility before adding it to a project. Also review recent releases to confirm support for your Laravel major version.
- How does native-cron install cron jobs on the server?
- It writes cron entries to the native crontab for the user running the PHP process. The server must have a cron daemon available and the process user must be permitted to manage its own crontab. Verify permissions and cron availability in staging before relying on it in production.
- Can I remove cron jobs managed by native-cron?
- Yes, the package is intended to install and remove crontab jobs from PHP. You should make removal part of your deployment or uninstall workflow so stale jobs do not remain on the server. Test removal behavior carefully because it changes real system state.
- What permissions are required to manage native cron jobs?
- The PHP process must be able to edit the crontab of the user it runs as, and the cron daemon must be running. In containerized or restricted hosting environments, crontab access may be unavailable or limited. Confirm with your hosting provider or infrastructure team before installing the package.
- Is native-cron suitable for production Laravel applications?
- It can be suitable when you need real system cron entries and understand that it modifies server state. Use it in staging first, ensure installs are repeatable, and monitor that jobs are actually running. Avoid unexpected crontab changes by controlling when install and remove operations execute.
- Does native-cron work on Windows servers?
- No, the package targets native unix cron, so it is intended for Linux and other Unix-like environments. Windows uses Task Scheduler instead of cron, so this package is not a fit there. Check your deployment platform before choosing it.
- How should I test native-cron without modifying my local crontab?
- Run tests in a disposable container or virtual machine where changing the crontab is acceptable. Avoid calling real install or remove operations in CI unless the environment is isolated. Review the package testing guidance and mock or disable system-level operations where possible.
Weaver
How can I help you explore Laravel packages today?