Looks promising, but a few questions

[juiceo]

Hey, stumbled upon this and it seems like something I would have a need for. I do have a few questions if you would be kind enough to answer :)

My use-case would be a single-deploy react + node app, where the backend would consist of pretty much only the json-cms. I would imagine using it something like this:

• Expose a route for the admin UI at e.g. /api/admin
• Expose a route for getting all of the json data in one request at e.g. /api/data
• Have a default data.json & schema.json stored in version control, which does not overwrite any changes made on the deployed version of the app on new deploys

As for the questions:

• Is it possible to run this as a module inside of a node.js app? How does that work?
• Does the library expose some sort of api for accessing the cms data, or do I need to create my own routes for accessing certain parts of the data?
• Is it possible to persist changes made via the visual editor between deploys, or will it always replace the data with whatever is in version control?

Thanks in advance :)

[xNok]

I have the same concernes on my side, This is perfect for my use case if I can get the current accessible via un endpoint.