779 B
779 B
Trade
dumb horizontal scaling (e.g. sharing app keys, failures)
for when nodes are infrequently made, and if data isn't shared it's not too bad
- read trusted registry key (called from cli)
- boot server self key (on server, readable by cli)
- read server key (encrypted to self)
- activate server (called from cli, sent to each server)
- send value (server to server)
- store keys/addrs
- read value (server to server)
todo
- deliniate path of trust for files
- e.g., tampering with registry public key
- tampering with local kv store
- bootable examples, practicality
- too many files (vs using sqlite or basis interface)
- separate out http server routes as optional (allow interfaces), swap to server folder