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

Create a backend disaster recovery plan #60

Open
3 tasks
dcdenu4 opened this issue Sep 9, 2022 · 2 comments
Open
3 tasks

Create a backend disaster recovery plan #60

dcdenu4 opened this issue Sep 9, 2022 · 2 comments
Assignees
Labels
backend Mainly a backend issue / task
Milestone

Comments

@dcdenu4
Copy link
Member

dcdenu4 commented Sep 9, 2022

This issue is for future work for when we have a public production web application. We'll want to at the very least:

  • backup the DB
  • setup cron job for whole disk snapshots
  • have a method to restore or spin up a new server in the case where something goes down.
@dcdenu4 dcdenu4 added the backend Mainly a backend issue / task label Sep 9, 2022
@davemfish davemfish added this to the release milestone May 30, 2024
@davemfish
Copy link
Contributor

I labeled with the release milestone because it seems like some of the work might be done alongside #107 and other deployment related issues.

@dcdenu4
Copy link
Member Author

dcdenu4 commented Sep 20, 2024

Since we're currently relying heavily on the single source SQL lite DB, I suggest that we set up a cron job to create snapshots of that DB in a google storage bucket. We can also try and capture the frontend cookies / data.

Otherwise, we could do a whole disk snapshot, but that might be overkill? At least, maybe we would do this less frequently?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Mainly a backend issue / task
Projects
Status: No status
Development

No branches or pull requests

2 participants