-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Database Backup on push #28
Comments
I like it! |
thumbs up! |
#bd0e1016f219be0a3 implements DB backups, they are stored in wp-content dir and follow this format: remote-dump-TIMESTAMP.sql |
Should this be re-opened? |
Why are you saying that @morrislaptop ? Both remote and local dump should be found in wp-content/ after every db push/pull operations |
Ah I was looking on the server for the backup when pushing. |
Oh no, they are all saved locally for security reasons :) |
It can be a useful feature a new cli option that offer a copy of the dump of the database before the push of it.
The problem is pretty simple: the files are often in a repo or in a compressed file somewhere (email, dropbox, filesystem, etc.), so if you made an error, you can revert everything, but if there are errors on the database, you can't.
It can be nice a new option that doesn't delete the dump of the database (and set it a new name like YYYYMMDDHHMMSS.sql in a htaccess protected folder) or save it in a dump.
The text was updated successfully, but these errors were encountered: