Download the PHP package microcode/filament-database-backup without Composer

On this page you can find all versions of the php package microcode/filament-database-backup. 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?

Example code of microcode/filament-database-backup

Informations about the package filament-database-backup

Filament Database Backup

Laravel 12 / 13 + Filament 4 / 5 plugin for database backup, restore, and scheduling.

Supports MySQL / MariaDB / PostgreSQL via CLI tools (mysqldump / mysql, pg_dump / psql).

Package: microcode/filament-database-backup
Namespace: Microcode\FilamentDatabaseBackup

Not supported: SQLite, application file backups, Spatie Backup.

Install

This package requires microcode/filament-integrations. Register both plugins on the Filament panel. Enable the aws driver if you want backups stored on S3.

Authorization is injected via ->authorize(...). Navigation group / icon / sort / cluster are configurable on the plugin. No host roles or clusters are hardcoded.

Filesystem disk

Add a private local disk (e.g. in config/filesystems.php). Dumps always start here; when AWS is configured this disk keeps only the latest .sql file.

Config key database-backup.disk defaults to backups.

S3 storage

When the Integrations AWS driver has access_key_id, secret_access_key, region, and bucket:

Host requirements:

  1. Enable aws on IntegrationsPlugin and save credentials in the Integrations UI.
  2. Define an S3 disk stub in config/filesystems.php (driver => s3).
  3. Install league/flysystem-aws-s3-v3.

Set DATABASE_BACKUP_S3_ENABLED=false to force local-only storage.

Retention

Global default (manual backups and S3 copies):

If omitted, config('database-backup.default_retention_days') is used (env DATABASE_BACKUP_DEFAULT_RETENTION_DAYS). Each schedule can override this for its own backups.

Cleanup runs after every successful backup and from database-backup:run-scheduled.

Queue worker

All create / restore / run-now work is queued.

Scheduler

In routes/console.php (or the host scheduler):

Command options:

Environment / config

Published file: config/database-backup.php

Key Purpose
disk Local filesystem disk name
path_prefix Folder under disk (default: slug of app.name)
s3.enabled / s3.disk Use S3 when AWS is configured; optional disk name override
queue / job_timeout Queue name and job timeout
process_timeout_seconds CLI process timeout
mysqldump_path / mysql_path / mysqldump_flags MySQL tools
pg_dump_path / psql_path / pg_dump_flags PostgreSQL tools
default_retention_days / retention_days_min / retention_days_max Retention window
tables.backups / tables.backup_schedules Table name overrides

Passwords are passed only via MYSQL_PWD / PGPASSWORD process env — never on argv or in logs.

Features

  1. Manual backup (queued dump → .sql on disk or S3 + catalog row)
  2. Restore with confirmation (queued; local cache or S3 download; ALL CURRENT DATA WILL BE LOST)
  3. Catalog sync from {path_prefix}/*.sql on the canonical disk
  4. Secure download route database-backup.download (authorize + path checks)
  5. Schedules: hourly / daily, optional per-schedule retention override
  6. Artisan database-backup:run-scheduled

Testing

Package tests use an in-memory SQLite connection for the catalog tables only. Dump/restore CLI paths are covered with callbacks / unit mapping tests — no real mysqldump is required.

License

MIT

All versions of filament-database-backup with dependencies

PHP Build Version
Package Version
Requires php Version ^8.4
filament/filament Version ^4.0|^5.0
illuminate/contracts Version ^12.0|^13.0
illuminate/support Version ^12.0|^13.0
livewire/livewire Version ^3.0|^4.0
microcode/filament-integrations Version ^1.1
spatie/laravel-package-tools Version ^1.16
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 microcode/filament-database-backup contains the following files

Loading the files please wait ...