dumb horizontal scaling via peer broadcast (e.g. sharing app cookie keys, devicecookie failures)
| cmd | ||
| example | ||
| file.go | ||
| get.go | ||
| go.mod | ||
| go.sum | ||
| kv.go | ||
| LICENSE | ||
| newreg.go | ||
| objreg.go | ||
| objserver.go | ||
| peerstore.go | ||
| privreg.go | ||
| privserver.go | ||
| README.md | ||
| regaddserver.go | ||
| regdelserver.go | ||
| routeget.go | ||
| routeintroduce.go | ||
| routeregister.go | ||
| routeset.go | ||
| servergenkey.go | ||
| set.go | ||
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