Skip to content
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

Prefix the db dump #54

Open
marcelovani opened this issue Apr 5, 2018 · 0 comments
Open

Prefix the db dump #54

marcelovani opened this issue Apr 5, 2018 · 0 comments

Comments

@marcelovani
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant