Clean-up strategy for db backups
mathew-fleisch opened this issue · 2 comments
mathew-fleisch commented
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.
magikid commented
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 commented
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.