I am way new to Node-RED and I would like to be able to collaborate with team members in order to develop a new solution for EVSEs. However, I do have some issues in mind that my team is in some trouble to figure out a proper solution.
Here is what is happening: We are trying to collaborate between multiple devs and, everytime one of us makes a change, that change overwrite what other people were working on. For example, imagine that I was working on "flow 1" but a colleague worked and deployed something on "flow 2". His change would get merged into my work but this "merge" would erase my work and place his in place. Bottomline is, I would have to do it all over again, after his deploy.
Is there a way to collaborate properly? someway to merge things but not erase other changes that are undergoing?
And also a curiosity. What would happen if I was working on flow 1, somebody else was also working on the same flow and we were implementing nodes on the same X and Y axis? What would happen if we tried to merge it?
Hello @gdziuba, I have taken a look at it and it seems to be promising but we are facing something more complicated... We are stuck at Node-RED v3.0.2 and we are unable to update it since we are using OEM hardware.
Is there any way possible to collaborate without relying on FlowFuse or Node-RED 4.0?
Interesting. I couldn't find any documentation on Node-RED. However, this sounds like an OEM discussion to see if they would provide a pathway to upgrade Node-RED, because there doesn't seem a way to get CLI access.
There are alternatives, but I imagine the hardware isn't changing given the usecase of the product.
Yeah, for now we are unable to change the hardware. We have already sent an e-mail to them in order to talk about upgrading Node-RED and also making FlowFuse and "Projects" feature available but still no response.
I appreciate the help, anyway.
Thank you so much @gdziuba.
