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.

Sign up for GitHub

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

Jump to bottom

Clean-up strategy for db backups #431

Open
mathew-fleisch opened this issue Jun 8, 2023 · 2 comments
Open

Clean-up strategy for db backups #431

mathew-fleisch opened this issue Jun 8, 2023 · 2 comments
Assignees
@mathew-fleisch

Comments

@mathew-fleisch
Copy link
Collaborator

The full database history is probably not necessary to save indefinitely and is (currently) 21gb. The db backup itself is (currently) 40mb compressed (~40%) and should also clean up old/unnecessary data as well as purge git history that is not needed.
@mathew-fleisch mathew-fleisch self-assigned this Jun 8, 2023
@magikid
Copy link
Collaborator

magikid commented Jun 8, 2023

I tend towards Digitalocean for all my cloud needs. I don't mind setting up a friends-of-DeSoto org in DO, inviting at least you and @jp00p, and donating s3 storage costs to host the backups there. What do you think of that?

@mathew-fleisch
Copy link
Collaborator Author

That's a good option though I think we "could" make the free option work for a few more years with a bit of clean-up automation.

@magikid magikid mentioned this issue Jun 8, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mathew-fleisch mathew-fleisch

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@magikid @mathew-fleisch