Download the PHP package jiannius/backup without Composer
On this page you can find all versions of the php package jiannius/backup. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
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 backup
Jiannius Backup
Scheduled database + files backup for Laravel apps: dump the database, zip it together with your configured folders, upload the archive to any Laravel filesystem disk, prune old archives — and email you when a backup fails.
Supports SQLite, MySQL, MariaDB, and PostgreSQL via spatie/db-dumper.
How it works
Each run produces a single timestamped archive — {app-slug}-2026-06-03-021500.zip — containing:
The archive is uploaded to the configured disk + path, then archives older than the retention period are pruned. Only this app's own archives (matching {app-slug}-*.zip) are ever deleted — unrelated files in a shared path are never touched.
Every failure is logged, and emailed if a notification address is configured. The command exits non-zero so your scheduler marks the run as failed.
Requirements
- PHP 8.3+ · Laravel 11+ host app
- The dump binary for your database on the server:
sqlite3,mysqldump,mariadb-dump, orpg_dump(setdatabase.binary_pathif it's not inPATH)
Installation
The service provider auto-registers. Publish the config if you want to override it:
Configuration
The quick knobs are env vars:
| Env | Default | Purpose |
|---|---|---|
BACKUP_DISK |
local |
Destination disk (any disk in config/filesystems.php) |
BACKUP_PATH |
backups |
Folder on that disk |
BACKUP_RETENTION_DAYS |
30 |
Archives older than this are pruned after each run |
BACKUP_NOTIFICATION_EMAIL |
— | Failure email recipient (unset = log only) |
BACKUP_DOWNLOAD_EXPIRY |
1440 |
Download-link lifetime in minutes (24h) for backup:list --url / backup()->list() |
Folders and database options live in config/backup.php:
With no folders configured, runs produce a database-only archive — that's the zero-config default.
Usage
Schedule it in routes/console.php:
Or run it programmatically — returns the uploaded archive filename, throws on failure:
List the archives already on the disk — each with a temporary download URL when the disk driver supports it (e.g. S3; local disks list with a null URL):
Or programmatically — returns a Collection of ['filename', 'path', 'size', 'date', 'url'], newest first:
Exit codes: 0 success · 1 backup failed (already logged/emailed) · 2 invalid flag combination.
Failure notifications
When a run fails for any reason — dump error, missing folder, upload rejected — the error is logged and a markdown email is sent to BACKUP_NOTIFICATION_EMAIL (if set), then the exception is rethrown. A broken mailer never masks the original failure.
Development
This is a package, so there is no artisan — Orchestra Testbench is the artisan:
End-to-end dump tests require the sqlite3 binary and skip cleanly when it's absent. See CLAUDE.md for the package conventions and docs/superpowers/specs/ for the design doc.
License
MIT.
