Comments (5)
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.
Related Issues (20)
- Use a single secret key for the node configuration
- Linking a contextId that's too long makes `signed=eth` unusable for other contextIds HOT 1
- redesign channel limits of profile service HOT 1
- get app generated ids in different expiration periods
- a bug in the consensus service
- remove constant parts of the wISchnorrPublic from GET /state
- support linking with Ethereum-signed messages for the soulbound apps
- limit the number of operations that every user/app should be able to send in a duration
- there is an issue in the "recovery connections" tests
- don't send duplicate sponsor operations
- [DRAFT] Change channel expiration behaviour HOT 2
- add appsOperationsLimit
- automate app registry HOT 3
- Sponsoring by contract should be able to accept both "HTTP" and "WS" PRC endpoints
- Adopt signature linking to v6
- Backend for recovery by seed phrase
- Stop calculating a verification per user for each app/expression in scorer
- Use incremental backup/restore for snapshots
- Remove other signing keys after social recovery
- Simplify Sponsoring
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from brightid-node.