Releases: gmemstr/database-janitor
Releases · gmemstr/database-janitor
Bugfixes
One Point Oh
Hey hey, 1.0! This version can now be considered stable, and production ready. Keep in mind you should never blindly run things in production environments though.
Updated docs coming soon.
Release Candidate 1
Considering this feature complete for v1, a lot of work to be done in optimizing the mysqldump-php library but meanwhile this can be tagged.
Changelog:
- Added "include" for using secondary configuration files
- e.g having a standard configuration file for all projects, then an additional project-specific config.
- Switched to custom fork of mysqldump-php library for better, more specific performance improvements
- Removed all instances of modifying the "real database"
- All manipulation (e.g removed data) happens during the dump
- Added specific
keep-data
configuration for keeping very specific rows from tables
Beta 3.1
Beta 3
Mostly focused on performance improvements, also added ability to load Drupal settings file for database settings (still requires database argument for now) and "kept rows" for trimming and scrubbing operations (see README).
./janitor --drupal=/var/www/path/to/settings.local.php
Beta 2
Initial Beta Release
Testing release! Includes core functionality:
- CLI interface with Symfony
- Simple YAML configuration
- Trimming and scrubbing of tables before a dump
- Sanitizing of table columns
Normal dump:
./database-janitor --host=dbhost --username=dbusername real | gzip -c > output/real_test.sql.gz
Trim dump:
./database-janitor --host=dbhost --username=dbusername --trim=true real | gzip -c > output/real_test.sql.gz