Download the PHP package blax-software/laravel-workkit without Composer

Laravel Workkit

A Laravel collection of helpers and utilities to reduce redundant code over multiple projects.

Features

• 💾 Streaming DB backups — mysqldump | xz | openssl in one pipe, APP_KEY-encrypted, zero DB bytes held in PHP memory (multi-GB safe)
• ♻️ Safe restores — --fresh wipes a dirty/partial schema before importing, after taking + verifying a recovery snapshot; failed imports never leave you stranded
• 🔎 Backup verification — workkit:db:verify proves a backup decrypts + is a complete xz stream without a database, so "is it corrupt?" gets a real answer
• 🧹 Retention pruning — age-based cleanup that always keeps the N newest, so prune can never delete your last recovery point
• 📊 Stats overview — workkit:stats prints per-model row counts, the largest tables, total DB size + a queue/backup summary
• 🩺 Queue health — workkit:queue:health reports per-queue depth/age/failed jobs and exits non-zero on breach (cron-friendly)
• 📄 Variable pagination — a #[VariablePaginatable] attribute + request()->perPage() macro for per-route, user-overridable page sizes
• 🧩 Reusable middleware & traits — bearer-token auth, force-JSON responses, HasExpiration, HasMeta, HasMetaTranslation, and small service helpers

Quick Start

Backups are encrypted with a key derived from your app's APP_KEY; a backup is restorable only by a deployment that knows the same APP_KEY.

Database Backups

A streaming, compressed, encrypted MySQL backup/restore suite. The dump, compression and encryption happen in a single shell pipe, so PHP never holds the database content in memory regardless of dump size.

Commands

Backup

Restore

--fresh is deliberately careful, because dropping every table is irreversible:

1. The source backup is verified before anything is touched — a file that can't be decrypted never triggers a wipe.
2. A pre-restore safety snapshot of the current database is taken and verified (skip with --no-safety-backup; the restore aborts if the snapshot can't be written, rather than wiping with no recovery point).
3. Only then are all tables + views dropped — via the same mysql client and database the import uses, so the wipe and the import provably hit the same server (a url DSN / unix_socket / read-write split can't make them diverge).
4. If the import fails after the wipe, the command prints the exact workkit:db:restore --file=<snapshot> command to recover.

Interactively, --fresh asks you to type the database name to confirm; under --force it proceeds non-interactively for deploy scripts.

Why --fresh and not just FK checks? A leftover table with an incompatible column type makes MySQL raise errno 150 / error 3780 at CREATE TABLE even with FOREIGN_KEY_CHECKS=0 (which restores already set). The only fix is an empty target. If a restore fails this way, the command tells you to re-run with --fresh.

Verify

Verify proves integrity (decrypts with this host's APP_KEY + a complete, non-truncated xz stream), flags a missing mysqldump completion marker (source-truncation), and compares the on-disk sha256 against the .meta.json sidecar. It does not prove restorability — a valid backup of the wrong or empty database still verifies "OK".

Prune

The --keep-min floor (default 5) is always kept regardless of age, so an aggressive --days can never leave you with zero backups. Schedule it:

Configuration

Requirements

The host needs mysqldump, mysql, xz, openssl and bash on PATH — standard on any reasonable Linux server. A non-empty APP_KEY is required (backups are unrecoverable without the key that produced them).

Restoring without the package

The output is plain openssl enc -salt format, so any host with the same APP_KEY can restore it directly:

Ops & Observability

Stats overview

Model row counts are estimated from information_schema on MySQL (instant); pass --exact for a real COUNT(*). Models are auto-discovered from app/Models — override with config('workkit.stats.models') (an explicit FQCN list) or models_path. Table/DB sizes are MySQL-only and degrade to "n/a" elsewhere.

Queue health

For the database queue driver it reports per-queue pending / due / delayed / reserved counts and the oldest due job's age, plus failed jobs (total + last N hours). It flags a queue STALLED — due work older than max_age_minutes with nothing reserved (the worker is probably down) — and exits non-zero on any breach so it slots straight into cron or a health probe. Thresholds live under config('workkit.queue.*'), with per-queue depth overrides for intentionally-slow queues. Schedule it:

Changelog

See CHANGELOG.md.

Star History