Download the PHP package nilanjank/scheduler-hub-laravel without Composer
On this page you can find all versions of the php package nilanjank/scheduler-hub-laravel. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download nilanjank/scheduler-hub-laravel
More information about nilanjank/scheduler-hub-laravel
Files in nilanjank/scheduler-hub-laravel
Package scheduler-hub-laravel
Short Description A Laravel scheduled-task dashboard with persistent run history and failure notifications (mail, Slack, webhook).
License MIT
Homepage https://github.com/nilanjank/scheduler-hub-laravel
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package scheduler-hub-laravel
🛰️ Scheduler Hub
A control center for Laravel's task scheduler.
See every scheduled task at a glance, trigger runs on demand, and never lose track of what happened — with a persistent run history and real failure alerts.
Why Scheduler Hub
Most Laravel scheduler dashboards stop at "here's a list of your cron jobs." Scheduler Hub goes further:
| 🗂️ Persistent run history | Every scheduled run — not just manual ones — is recorded automatically by hooking into Laravel's native scheduler events. History stays accurate even if nobody ever opens the dashboard. |
| 🔔 Failure notifications | Mail, Slack, and signed generic webhooks, each independently toggleable. Know the moment something breaks, wherever your team already looks. |
| 🆔 Stable task identity | Tasks are identified by a hash of their command, expression, timezone, and description — not their position in the schedule list — so the "Run" button always hits the task you meant, even if the schedule changes between page load and click. |
| 🎨 Clean, fast dashboard | Live search, type filters, status badges, and an in-browser output viewer. No build step, no JS framework — just a single Blade view. |
| 🔒 Locked down by default | Disabled out of the box. Gate-based or callback-based authorization, configurable middleware, and manual execution off unless you explicitly turn it on. |
Requirements
| Laravel | PHP |
|---|---|
| 11.x | 8.2+ |
| 12.x | 8.2+ |
| 13.x | 8.3+ |
Installation
Quick start
Visit http://localhost:8000/scheduler-hub 🎉
To allow the Run now button:
The Tasks tab lists every registered task with its next run and, if history is on, its most recent run status. The History tab shows every recorded run, filterable by status, with full output/error on click.
Configuration
Everything lives in config/scheduler-hub.php:
🔒 Security
The dashboard is disabled by default. To use it in production:
The default Gate only allows access in the local environment. Define it
yourself for anything else:
Or use the authorize config callback instead of a Gate:
⚠️ Never mount this behind only
['web']middleware on a public app.
🔔 Notifications
Enable the channels you want:
Mail and Slack fire on failure by default (notify_on). The generic
webhook always fires for whichever statuses are in notify_on, so it can
double as a success ping too if you add success to that list.
Webhook requests are signed with an X-Scheduler-Hub-Signature header
(HMAC-SHA256 of the raw JSON body) whenever a secret is configured — verify
it on the receiving end before trusting the payload.
🗑️ Run history retention
Old runs don't accumulate forever — schedule the built-in prune command:
Retention window is controlled by history.retention_days in the config.
License
Released under the MIT License.
All versions of scheduler-hub-laravel with dependencies
illuminate/console Version ^11.0||^12.0||^13.0
illuminate/contracts Version ^11.0||^12.0||^13.0
illuminate/database Version ^11.0||^12.0||^13.0
illuminate/http Version ^11.0||^12.0||^13.0
illuminate/notifications Version ^11.0||^12.0||^13.0
illuminate/support Version ^11.0||^12.0||^13.0