I've been playing with node-red for awhile now as a hobby but dreaming I could use it on my day job where we create RESTful json apis using node.js.
After looking pretty hard I've not found good solutions to:
a. All the flows in one giant json file (we will have hundreds of flows created by different teams where we have to restrict access who can access and edit which flows - having all that in one single giant json file is a non-starter)
b. Storing the flows in a database instead of the file system (I've studied the storage api and tried out e.g. node-red-flows-mongo but am I right the save part of the storage api assumes you are saving all the flows at once i.e. "a" above).
I know a lot has been happening re the editor/run-time split and the 1.0 beta release - is there anything with this work that would provide hooks I could plug-in to customize the above?
e.g. I wish the editor and storage api had something where the user would save their changes to the flow on a single tab and POST the json for just that flow to be saved.
The closest I see to that is saveLibraryEntry but I confess I've not tried to use the library features at all... is it conceivable I could save each of my tabs flows as individual "library entries" as database records, and then have my "getFlows" query those to dynamically aggregate back together the giant all-flows json?
Or can anybody think of anything better?