Backups for docmost + nocodb #152
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add some backup cronjobs for nocodb and docmost!
These are kinda rough/ready backups. Both nocodb and docmost have a storage directory (for images etc), and also of course data in their respective database.
How does the restore process work? Yes
Where are the backups stored? On a hetzner storage box (another ~3.5 eur/month)
How can we extract the backups if we ever need them? At present, I'm the only one with the keys here. I'll do some thinking about the best way to share this. (see below)
Why did we need new containers? I couldn't find any open/maintained images that had both psql + ssh. It would be nice to not have to manage some containers, but not the end of the world. Could also manage this automagically with github actions in theory.
Storage box file structure:
☝️ Each individual service (docmost/nocodb) has it's own set of ssh keys to access the storage box. This means if one service gets pwned, at least it doesn't pwn the other. The good news is that I had some foresight to have a separate account for the
k3sdirectory, which means we could create some ssh keys there, and share them in the keepass for emergency access etc.