Currently, Scribe-Server is already serving the .sqlite versions under the /packs path. In planning for the ideal state of Scribe-Server, an implementation storing all data in a DB, managing data history, and then allowing for filtered client requests seems to be a good objective. However, that does require a non-trivial amount of development on both the Scribe-Server and Scribe-Data side.
This issue is for trialing an alternative to serving the language packs for the Scribe apps. Could simply serving the .json Scribe-Data files suffice for now to implement data downloads in Scribe apps?
Terms
Issue
Currently, Scribe-Server is already serving the
.sqlite
versions under the/packs
path. In planning for the ideal state of Scribe-Server, an implementation storing all data in a DB, managing data history, and then allowing for filtered client requests seems to be a good objective. However, that does require a non-trivial amount of development on both the Scribe-Server and Scribe-Data side.This issue is for trialing an alternative to serving the language packs for the Scribe apps. Could simply serving the
.json
Scribe-Data files suffice for now to implement data downloads in Scribe apps?