Create regular DB dumps about brightid-node HOT 5 CLOSED

Could be done with a cron in the db container that then puts them in a docker volume

from brightid-node.

There is some intermediate code to support this in this commit b39ad08 . I think in this commit, I started making a second dockerfile so that a node operator could decide whether to run a version that creates automatic backups or not. (Probably not all nodes need to do this).

from brightid-node.

Where do you think the backup should be hosted remotely? another node? would it make sense to add functionality so that nodes can create backups and/or download other backups and host backups themselves?

from brightid-node.

I don't know where backups should be publicly hosted. Let's provide node operators with instructions on how to manage the backups that are saved on their node, and they can make that decision for themselves. I think for us (node one), I would host them on cheap cloud storage and have a dns name pointing to it. Maybe ipfs is another option.

At some point, there will need to be a standard way of retrieving and applying the most recent backup for new node operators, and by then there will need to be a recommended way to host backups, but that's not what this issue is about.

from brightid-node.

There could be a new foxx app (not BrightID) just for downloading the (compressed tar) file if that's easier than downloading the file from docker. It would not be public, though. Figuring out how to publicly host these files is beyond the scope of the issue.

from brightid-node.