Closed hkirsman closed 4 months ago
Based on @deiviic comment I've added skipping of cache tables in the import. In one of the real case scenarios the difference of dump file was from 517MB to 86MB.
I'm thinking of re-ordering the commands a bit - instead of dropping the db, that should be done after import worked. In case you forget to enable VPN, db would be dropped, but why do it before if the most error prone task could fail.
Or maybe just remove the drop. ddev import should do that.
instead of dropping the db
Do we have to drop it? At lando clears DB before doing import - have not checked if ddev does the same.
instead of dropping the db
Do we have to drop it? At lando clears DB before doing import - have not checked if ddev does the same.
Yeah, we don't need extra drop. I've tested that import works fine without extra drop and there's also extra command not to drop
Overview
In Lando we have syncdb command that imports production database via SSH tunnel and imports the db into local env. This is adding the same feature to this project.
The logic of the script:
Testing
lando syncdb
works in Lando:ddev syncdb