Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, from what I can tell, running
genesis:up
(orgenesis:up:db
) overrides the staging/prod db without generating a backup: https://github.com/genesis/wordpress/blob/master/deployment/lib/sync.rb#L123-L138Right now, we've got a "missing posts" issue with nursing.org staging. I haven't been able to to pin it down to any
:up
commands being run, but it does seem like a useful thing to create a backup of the staging db before overriding it with local. Two ways we could do that:/#{deploy-branch}/backups/
(something already created a few .sql files there for nursing, but I'm not sure what) - we'll want to figure out how to keep just a few to prevent server bloat with sql dumps.:backup
task w/no modification)Thoughts?