You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Background
When the command to import the database is executed, it will copy the file from the remote location to /tmp folder. Next time you run the command, it will check if the dump has been modified to avoid copying the file again, this saves time.
The problem
If the dump has the same name for all the sites, i.e. latest.sql.gz, and you download the dump for two different sites, the functionality above will not work, because the files will be different
Proposed solution
Prefix the dump or put the dump into a subfolder, so that when the copy happens, it doesn't replace the existing dump for another site.
Also, Devops suggested not using /tmp to store the dumps, but the home folder i.e. ~/tmp
The text was updated successfully, but these errors were encountered:
Background
When the command to import the database is executed, it will copy the file from the remote location to /tmp folder. Next time you run the command, it will check if the dump has been modified to avoid copying the file again, this saves time.
The problem
If the dump has the same name for all the sites, i.e. latest.sql.gz, and you download the dump for two different sites, the functionality above will not work, because the files will be different
Proposed solution
Prefix the dump or put the dump into a subfolder, so that when the copy happens, it doesn't replace the existing dump for another site.
Also, Devops suggested not using /tmp to store the dumps, but the home folder i.e. ~/tmp
The text was updated successfully, but these errors were encountered: