Download the PHP package brimham/filament-backup-monitor without Composer
On this page you can find all versions of the php package brimham/filament-backup-monitor. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download brimham/filament-backup-monitor
More information about brimham/filament-backup-monitor
Files in brimham/filament-backup-monitor
Package filament-backup-monitor
Short Description Filament panel for brimham/backup-monitor — run history and last-backup-per-destination health for spatie/laravel-backup.
License MIT
Homepage https://brimham.app
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 filament-backup-monitor
Filament Backup Monitor
A Filament panel for brimham/backup-monitor — see the history of every spatie/laravel-backup run and the last backup per destination at a glance.
The core brimham/backup-monitor package records each backup run to a backup_runs table. This package surfaces that history inside your Filament admin panel:
- a run-history table — every backup, health-check and cleanup with its status, destination, size and timestamp
- a "last backup per destination" health panel — the most recent run for each disk, so a silently failing destination is obvious
This is the free core. Proactive alerting on missed/silent failures and a multi-site dashboard live in Pro — see Upgrade to Pro.
Screenshot
Requirements
- PHP 8.3+
- Laravel 12 or 13
- Filament 3, 4 or 5
- brimham/backup-monitor (installed automatically)
Installation
Run the core package's migration if you haven't already:
Usage
Register the plugin on the panel where you want the backup history to appear:
A Backups item appears in the panel navigation, linking to the run-history page with the health panel at the top.
Upgrade to Pro
This panel shows you the history of backups that ran. It can't show you the backup that silently stopped running — there's no event to record, so a destination that quietly dies just stops updating while everything still looks fine. That's the failure that actually loses data. Brimham Backup Monitor Pro closes that gap:
- Missed / overdue detection — a dead-man's-switch that flags any destination whose last successful backup is older than its expected cadence (or has never run).
- Multi-channel alerting — mail, Slack, Discord, Teams, and webhooks, de-duplicated and escalating, with recovery notifications.
- External heartbeat — ping healthchecks.io / Cronitor as backups run, catching an outage even if the whole app and scheduler are down.
Running backups across many sites? The Filament Backup Monitor Collector is a companion Filament plugin that ingests every install's health snapshot into a single multi-site dashboard — overdue destinations, last successful backup, and installs that have gone quiet, all in one panel.
License
MIT. See LICENSE.
All versions of filament-backup-monitor with dependencies
brimham/backup-monitor Version ^0.1.1
filament/filament Version ^3.0 || ^4.0 || ^5.0
illuminate/contracts Version ^12.0 || ^13.0
illuminate/support Version ^12.0 || ^13.0