v1.0.3

Fixes plugin startup failing with Feature 'database-exporter' already exists when feature registrations are already present, including in Vito's configuration cache. Vito can automatically disable the plugin after this error, leaving exporter routes unavailable on subsequent requests.

Feature and action registration now independently skip existing entries. The cached-route naming fix from v1.0.2 is retained.

Recovery: update to v1.0.3, then enable Database Exporter again under Admin → Plugins. Updating alone does not restore the enabled state. Verify with php artisan route:list --name=database-exporter from the Vito directory as the application user; nine routes should appear.

Validation: 6 regression tests, 246 assertions, covering repeated boot, pre-existing feature/action configuration, cached and uncached routes, and the server feature link. PHP syntax, Composer validation, and diff checks pass.

v1.0.2

Fixes Route [database-exporter.index] not defined when opening Vito server features with Laravel route caching enabled.

All nine exporter routes now receive their names before registration, making their URLs available in both cached and uncached route collections.

Validation: 2 regression tests pass with 76 assertions, covering URL generation, endpoint matching, middleware, and the server feature link. PHP syntax checks and Composer validation also pass.

Update the Database Exporter plugin to v1.0.2 in Vito to apply the fix.

v1.0.1

Document the required trailing slash for installation on Vito releases whose GitHub URL parser can trim the final t from repository names ending in Export. Plugin functionality is unchanged.

v1.0.0

Initial release of VitoDeploy Database Exporter. Includes queued native MySQL, MariaDB, and PostgreSQL exports; remote and local disk checks; private temporary storage; authenticated expiring downloads; SHA-256 verification; cleanup; cancellation and retry; and a responsive Vito-style GUI.