Download the PHP package xve/laravel-db-export without Composer

On this page you can find all versions of the php package xve/laravel-db-export. 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 xve/laravel-db-export

Informations about the package laravel-db-export

Laravel DB Export

A Laravel package for database exports with profile-based exclusions, anonymization, and zero-impact exports.

Features

Installation

Publish the configuration:

Configuration

MySQL/MariaDB Binary Path

If mysqldump is not in your PATH, set it in config/db-export.php or .env:

MariaDB Compatibility

For MariaDB, ensure MySQL-specific options are disabled:

Cleanup Old Exports

Automatically delete old exports before creating new ones:

Commands

Setup / Find mysqldump

Find the mysqldump binary and get configuration instructions:

This command searches common locations for mysqldump and displays:

List Profiles

Estimate Export Size

Export Database

Prune Exports

Delete all export files:

Export Profiles

Profile Description
default Clean export with structure-only for logs/cache/sessions and anonymized PII
inspection Only telescope and audits (for debugging)

Command Options

Table Selection

Output Options

Other Options

Examples

Standard Export

Exports everything with structure-only for logs/cache/sessions and anonymized PII.

Include Audit Data

Override structure-only to include audit data.

Debug Export

Exports only telescope and audit tables for debugging.

Specific Tables

Export only the tables you need — no profile required:

Structure Only (No Data)

Profiles Configuration

Define custom profiles in config/db-export.php:

Anonymization Strategies

Anonymization works with or without fakerphp/faker. If faker is installed, you get realistic fake data. Without it, simple fallbacks are used (e.g., User_a1b2c3d4, [email protected]).

Preserve Admin/Developer Accounts

Skip anonymization for rows where specific columns match certain email domains:

Users with @xve.be or @company.com emails will keep their original data while all other users are anonymized. Each table can specify which column to check.

Production Usage

Zero-Impact Exports

The Problem: Traditional mysqldump commands can severely impact production databases:

The Solution: This package uses mysqldump options that eliminate these issues:

Option Problem Solved
--single-transaction Creates a consistent snapshot using InnoDB's MVCC. No table locks, writes continue normally.
--quick Streams rows directly to output instead of buffering in memory. Handles multi-GB tables without memory issues.
--skip-lock-tables Prevents LOCK TABLES command that would block all writes.

With these options, you can safely export a production database while the application continues serving requests with no degradation.

Best Practices

  1. Use a read replica for exports when possible:

  2. Schedule during low-traffic hours

  3. Use structure-only for large tables like audits:

  4. Monitor during export:

Output Location

Default: storage/app/db-exports/

Files are named: {database}_{date}_{time}_{profile}.sql.gz

Example: my_app_2026-01-15_14h30_default.sql.gz

See Also

License

MIT

All versions of laravel-db-export with dependencies

PHP Build Version
Package Version
Requires php Version ^8.2
illuminate/contracts Version ^10.0|^11.0|^12.0|^13.0
illuminate/database Version ^10.0|^11.0|^12.0|^13.0
illuminate/support Version ^10.0|^11.0|^12.0|^13.0
spatie/db-dumper Version ^3.4
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 xve/laravel-db-export contains the following files

Loading the files please wait ...