Skip to content

Design database/datastore approach #3

@kstapelfeldt

Description

@kstapelfeldt

Based on output here: https://docs.google.com/spreadsheets/d/11S4Hc4ky50lClzfn74f8B3MqqHB9_YRTEvEjBkOX634/edit#gid=649117397

Do we need a postgres database? Or keypair store? Something else?

Produce schema if necessary

We need a pretty picture, please :) - embed in an .md

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions