- Is mczolko/heroku-scheduler-bundle a Laravel package?
- No. It is a Symfony bundle that integrates Heroku Scheduler with a Symfony application through Symfony's Bundle and dependency injection model. It does not map onto Laravel's service container or package auto-discovery. Laravel applications should use Laravel's native scheduler instead.
- Can I use mczolko/heroku-scheduler-bundle with Laravel 10 or 11?
- There is no practical integration path for modern Laravel. The package is built for Symfony bundle registration, and its Composer constraints are likely PHP 5.x and Symfony 2.x era. Those constraints will probably conflict with PHP 8.x and the Symfony components Laravel 10/11 already ship. Do not force installation with --ignore-platform-reqs.
- How do I install mczolko/heroku-scheduler-bundle?
- It would be installed with Composer as a Symfony bundle and registered in a Symfony kernel, not through Laravel package discovery. For a Laravel application there is no supported installation path. Treat it as a reference implementation rather than a dependency.
- What is the Laravel alternative to heroku-scheduler-bundle?
- Use Laravel's native scheduler in App\Console\Kernel::schedule() and have the Heroku Scheduler add-on invoke php artisan schedule:run on a one-off dyno. Laravel provides withoutOverlapping(), onOneServer(), per-job timeouts, and observability primitives. That approach avoids pulling in an unmaintained Symfony bundle.
- Is mczolko/heroku-scheduler-bundle maintained?
- No. The last release was 2016-03-17, and the project has 1 star and 0 dependents. There is no visible CI, test suite, or security posture. Any fork or port becomes your team's responsibility to own.
- What PHP and Symfony versions does heroku-scheduler-bundle support?
- Its Composer constraints are likely from the PHP 5.x and Symfony 2.x era. That will conflict with PHP 8.x and Symfony 6/7 components used by modern Laravel versions. Verify resolution before considering it, but expect conflicts and do not bypass platform requirements.
- How does Heroku Scheduler work with Laravel?
- Heroku Scheduler is a platform add-on that runs one-off dynos on a coarse cadence such as every 10 minutes, hourly, or daily. For Laravel, configure it to run php artisan schedule:run, and let Laravel's scheduler decide which jobs execute. Overlap control, retries, and alerting still need to be designed by the application team.
- Is it safe to use mczolko/heroku-scheduler-bundle in production?
- It carries high technical risk for production. The package is effectively unmaintained, has no visible tests or security process, and CVEs would go unpatched. Supply-chain risk is low because the package is tiny, but bit rot risk is near-certain.
- What should I do if I inherited a Symfony app using heroku-scheduler-bundle?
- Migrate the scheduled entrypoints to native Symfony console commands invoked directly by Heroku Scheduler. Then remove the bundle, because it is doing orchestration the platform already provides. Inventory jobs, cadences, overlap requirements, and idempotency before cutting over.
- Does heroku-scheduler-bundle do anything beyond wrapping Heroku Scheduler command invocation?
- It is almost certainly a thin wrapper around invoking console commands from Heroku Scheduler. Porting that behavior into a Laravel console command or native Symfony command is cheaper than adapting the bundle. Confirm the real job inventory, cadence, overlap, idempotency, and retry semantics before deciding.