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
{{ message }}
This repository has been archived by the owner on Apr 14, 2019. It is now read-only.
Can you provide more details? I feel like a dumb/simple approach is better than a smart/complex approach when it comes to disaster recovery.
I'd be afraid this would complicate the restore process. Right now it's a simple gunzip backup.sql.gz | mysql command to restore. If we're dealing with json paritals, how do you apply them once the schema has changed?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Rather than back up the entire database, we can use
LogEntry
to identify models that have changed, and to dump their information to a json file.We should alert admins when a
LogEntry
has a newer date than the json file.The text was updated successfully, but these errors were encountered: