-
Notifications
You must be signed in to change notification settings - Fork 61
Conversation
fixed
✅ Deploy Preview for ubiquibot-staging ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Keyrxng Could you reopen the current PR to this public repo https://github.com/ubiquity/ubiquibot-db-backups ? Once it is merged I'll make it private.
@Keyrxng What should be specified in the |
@pavlovcik We need to set the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works fine, dumps are created https://github.com/ubiquity/ubiquibot-db-backups
Closing the current PR because the "DB backup" workflow is implemented here
Resolves #865
Quality Assurance:
Considering this will be ran in a private repo, it was difficult to think of a way to showcase it and this was the best way I could think, mobile users beware.
I wasn't sure if you'd want to keep previous dumps so I've timestamped each and the restore action looks for dump files with no timestamp. I wasn't sure of a cleaner way to do this, I considered just backing up straight to another Supabase instance but this was there's a history of backups I guess.
Pushing the backup files you want to use into a branch called restore will restore things, I felt this was the cleanest way with my understanding that restores would rarely ever need to happen
Dump Commit
Restore Action
Empty DB
Restored DB