From last 2 days, I am trying to look out for possibilities of having multiple users login to editor and not disturb each other by having separate flow files.
My current approach -
Maintain session IDs for each user login externally by using Redis and at the same time assign/map a flow file dedicated to a user session ID. For example if Gaurav logs in assign a session ID along with file name - "flows_gaurav.json". And finally inside the RED.js instead of picking flowFile as a global var, picking it from session object, so as to have separate flows getting used by the Editor for separate sessions.
But I am not yet familiar with Node-RED code and obviously I don't know the main vision behind the way it has been developed. So I assume that for some very important reason, the editor has been kept a single user instance. But please do guide me if we can achieve things in this way within Node-RED.
I am not sure if I am making sense here, but I am sure you guys will suggest and guide better!
For Info - As of now, we are able to spin multiple instances/pods of Node-RED (inside k8s cluster) for separate users. When I use the term "we", I mean, me and my team who are working on Node-RED solutions!
But still, I think if we can have multiple users in a single instance, the kind of value and dynamics we can achieve from NR will be manifolds.