- What is nwidart/db-exporter used for?
- It is a Laravel package for exporting database tables from a web interface, with configurable table selection and multiple output formats. It can be used for backups, moving data between environments, or generating quick dumps for analysis. The package also describes Artisan command integration for export and backup workflows.
- How do I install nwidart/db-exporter in Laravel?
- Install it with Composer using the nwidart/db-exporter package name, then follow the package documentation for service provider registration and configuration publishing. On Laravel versions with package auto-discovery, registration may be automatic, but the available release notes do not confirm this for every version. Verify the exact commands and config file location in the package source or README before relying on it.
- Which Laravel versions does nwidart/db-exporter support?
- The available release information points to Laravel 5 support, specifically release 1.1 described as support for Laravel 5. It does not establish support for Laravel 6 or later, and the release notes do not list exact Laravel 5 minor versions. Treat modern Laravel compatibility as something to verify with a spike and Composer constraints before adoption.
- Which databases can nwidart/db-exporter export from?
- The package is described as driver-based, with support for MySQL, PostgreSQL, SQLite, and more. Actual behavior can vary by driver and Laravel version, especially for schema features such as foreign keys, views, triggers, or procedures. Confirm the specific database engine and schema features you need in a test environment.
- What export formats does nwidart/db-exporter support?
- It supports multiple formats such as CSV, Excel, PDF, and JSON. The web interface lets you choose the tables and output format before downloading the result. Check the package configuration and source for the exact format drivers available in your installed version.
- How do I configure which tables are exported or ignored in nwidart/db-exporter?
- Configuration is handled through the package config file, which can define table lists, ignored tables, and export options. You should publish or edit that config according to the package documentation for your version. If you need per-environment rules, keep them in environment-specific config and test the resulting table selection.
- Can nwidart/db-exporter handle large database tables?
- The package describes chunked exports designed to handle large datasets safely. Chunking reduces memory pressure but does not remove database, PHP, or web server time and memory limits. For very large tables, test export duration and tune chunk size, timeouts, and storage paths before using it in production.
- Does nwidart/db-exporter include Artisan commands for backups or exports?
- The package overview mentions Artisan command integration for quick backups and exports. The exact command names, options, and whether they cover remote sync should be confirmed from the package source for your pinned version. Artisan commands are useful for scheduled backups, but you still need retention, encryption, and monitoring policies.
- Is nwidart/db-exporter safe to use in production?
- Treat production use carefully because database exports can expose sensitive data and consume significant resources. Review credential handling, storage locations, access control, PII exposure in seed or export files, and any remote-sync behavior before enabling it. The available notes do not describe security fixes or a support window, so add guardrails and test on non-production data first.
- Is nwidart/db-exporter actively maintained, and what are the alternatives?
- The available information shows a release adding Laravel 5 support but no clear ongoing maintenance cadence, security fixes, or dependency updates. For long-term use, pin the exact version, consider forking and owning it, or evaluate maintained Laravel backup and export tools. A time-boxed spike and schema-fidelity tests will help you decide between adoption, a fork, or an internal reimplementation.