Closed iduuck closed 6 years ago
Hm...I understand your fear :)
Wordmove will always save a dump of the remote database inside the wp-content/
folder anyway, so if you'll blank the remote db my mistake, you'll have the dump to restore manually.
A really raw way to lock the push is to comment out the database section inside the Movefile
.
Could these informations helps?
Would be nice as a feature. To be able to add something to the wordmove file like block push/pull of database/template/uploads etc.
block-push:
-database: true
Because: I might get a database back-up, but what if I overwrite the uploads folder? Of course I should always have a proper backup, but at least this would save the work of restoring from the backup, including the downtime caused by this.
My fear is that than WordMove would require an alarm to remember us to add the lock option! Out of jokes ;) I'm tagging as a feature request and we'll elaborate a bit on this.
My bigger concern is to try to avoid an excessive grow of the Movefile, but the feature should be achieved by other ways.
Thanks for your interventions
It's just growing, if needed. And I would rather have a bigger Movefile than a broken service. On Fri 28 Aug 2015 at 11:38 Alessandro Fazzi notifications@github.com wrote:
My fear is that than WordMove would require an alarm to remember us to add the lock option! Out of jokes ;) I'm tagging as a feature request and we'll elaborate a bit on this.
My bigger concern is to try to avoid an excessive grow of the Movefile, but the feature should be achieved by other ways.
Thanks for your interventions
— Reply to this email directly or view it on GitHub https://github.com/welaika/wordmove/issues/205#issuecomment-135717335.
Closed by #447 🎉
Is it possible to lock the push to the database. Let's create a use case:
wordmove push --all