Summary
The README mentions that the storage backend currently uses SQLite and that PostgreSQL support is "coming soon". I couldn't find an open issue tracking this work, so opening one to discuss scope and subtasks.
Motivation
- PostgreSQL is more suitable for production deployments than SQLite in many environments.
- Having a clear tracking issue can help contributors (like me) pick up well-scoped pieces of the work.
Initial thoughts / possible subtasks
Questions
- Do you already have an internal design for the PostgreSQL backend?
- Would you be open to community contributions on smaller parts ?
I'm a student contributor and I might not be able to implement the entire feature, but I'd like to help with some pieces if possible.
Summary
The README mentions that the storage backend currently uses SQLite and that PostgreSQL support is "coming soon". I couldn't find an open issue tracking this work, so opening one to discuss scope and subtasks.
Motivation
Initial thoughts / possible subtasks
Questions
I'm a student contributor and I might not be able to implement the entire feature, but I'd like to help with some pieces if possible.