Download the PHP package pagerlite/pagerlite-laravel without Composer

On this page you can find all versions of the php package pagerlite/pagerlite-laravel. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

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 PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • 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.
Please rate this library. Is it a good library?

Informations about the package pagerlite-laravel

PagerLite

Latest Version on Packagist Tests Code Style Total Downloads

A dead-simple, self-hosted on-call and paging system for Laravel — in the spirit of Horizon and Telescope. Install the package, visit /pagerlite, add your team, and drag someone onto the calendar: when an incident comes in, PagerLite notifies whoever is on call and escalates until somebody acknowledges. Everything lives in your own database; no data ever leaves your app.

Features

Requirements

Installation

Require the package with Composer:

Then run the install command:

It publishes the configuration and the pre-built dashboard assets, and offers to run the migrations (four pagerlite_-prefixed tables). Then:

  1. Set a token in .env so external tools can report incidents:

  2. Run a queue worker — escalation is driven by delayed queue jobs:

  3. Visit /pagerlite, add members, order the escalation chain, and put someone on call.

Dashboard authorization

Out of the box the dashboard is only accessible in the local environment. To open it up in other environments, register an authorization callback — typically in a service provider's boot method:

Acknowledge and resolve actions are attributed to your app's authenticated user.

Reporting incidents

From anywhere, over HTTP

title is required; message and service are optional. The endpoint responds 201 with the incident's id and status. For tools that can't set headers, the token may be passed in the URL instead: POST /pagerlite/api/events/{token}.

Every request creates a new incident — PagerLite does not deduplicate, so point your monitoring's state change hook at it, not its every-minute check.

From your own code

How paging works

  1. An incident is recorded, and the current on-call member (from the schedule) is notified.
  2. If nobody is on call, the escalation chain is paged from the top instead.
  3. If the incident isn't acknowledged within the escalation timeout (5 minutes by default), the next member of the escalation chain is notified — skipping whoever is already on call — until the chain is exhausted.
  4. Acknowledging the incident from the dashboard stops the escalation.

The schedule operates on UTC days: shifts hand over at midnight UTC, and every member sees the same calendar regardless of their timezone.

Embedding the calendar

Set a secret in .env:

The read-only calendar is then available — without logging in — at:

Drop it into an iframe on a wiki or status page:

Anyone with the link can see who is on call (names and schedule only — no incidents, no editing). Leave PAGERLITE_EMBED_TOKEN unset and the embed URL does not exist.

Configuration

The published config/pagerlite.php covers everything; each option also has an environment variable:

Variable Default Purpose
PAGERLITE_PATH pagerlite URI path where the dashboard is served.
PAGERLITE_TOKEN Bearer token required by the events endpoint.
PAGERLITE_EMBED_TOKEN Secret enabling the public read-only calendar. Unset = disabled.
PAGERLITE_ESCALATION_TIMEOUT 300 Seconds to wait for an acknowledgement before escalating.
PAGERLITE_USER_MODEL App\Models\User Host-app user model that acknowledge/resolve actions are attributed to.

Upgrading

After updating the package, re-publish the dashboard assets:

(or simply re-run php artisan pagerlite:install).

TODO

License

PagerLite is open-source software licensed under the MIT license.


All versions of pagerlite-laravel with dependencies

PHP Build Version
Package Version
Requires php Version ^8.4.0
inertiajs/inertia-laravel Version ^2.0.4
laravel/framework Version ^12.20.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package pagerlite/pagerlite-laravel contains the following files

Loading the files please wait ...