Consisted of three tasks:
This work is funded through NGI0 Commons Fund, a fund established by NLnet with financial support from the European Commission’s Next Generation Internet program. Learn more at the NLnet project page.
To start with, the template repository containing the original Node-RED editor needs to be updated. This repository has a running, working Node-RED instance with a version of 4.0.9, which provides the basis for the Erlang-Red flow editor.
The template was upgraded to Node-RED 5.0.8. The codebase was then retrieved from the template using a script to copy the code into the Erlang-Red repository. The retrieve script was also updated to include new assets.
Essentially, a compiled minified version of the Node-RED editor is included in Erlang-Red, while the original editor is in the template repository.
When I copied the editor codebase to Erlang-Red, I made changes for Erlang development. For example, Erlang has different number formatting than JavaScript, so I had to extend some things in the editor. I did that basically by hand in the codebase. When I then update the editor, those changes need to be ported to the new version.
How did I do that? Basically, it was a couple of steps I had to take. First, I had to identify all the changes I made to Node-RED for Erlang-Red. So, I took the original 4.0.9 Node-RED editor, took a copy, and installed it into the Erlang-Red codebase.
Then I did a diff on the editor template codebase versus the codebase inside of Erlang-Red. From those changes, I created a graph of tasks that represented changes that represented specific behaviour I had added.
That became the project plan for this task:

This plan is just a visual representation of all the changes I made to the editor version 4.0.9 to improve support for Erlang development. The plan is just a collection of tasks which in turn were diffs of the codebase.
Some changes were actually ported back to the Node-RED editor itself, so I didn’t have to make those changes. Those are the tasks in the overview which are yellow. Those are back-ported changes that are made and then provided to the Node-RED community because they were general fixes. So, they were actually already included when I upgraded to version 5; I didn’t have to port those changes back.
The tasks marked in red are things that I still have to work on, for example, the background color of the top panel - that’s not as easy to change as it was in Node-RED 4. So, this is my project plan for that part, porting the editor to version 5.
After having done that, I ported the back-end, specifically the FlowHubⓁ server-side backend.
The third component was upgrading the nodes and plugins which come with the editor. Which meant that I actually had to implement the back-end for FlowHubⓁ.
Currently, I have a working Node-RED version of local visual change management server. Basically the backend APIs tunnel the requests to the FlowHubⓁ server currently running in a Node-RED instance in on my local machine.
For this task, I also created a project plan that tracked the various API endpoints I had to implement in Erlang-Red.
[{"id":"4c1d134ac16b473b","type":"tab","label":"[Ered Tasks] FlowHub Backend","disabled":false,"info":"","env":[]},{"id":"1579ec8387f78888","type":"junction","z":"4c1d134ac16b473b","x":917.1671876907349,"y":1142.45263671875,"wires":[["9f1418770f9d9217","64ac5e43c2fd068f","8fde532e6320d5e8","2f655018b6bce854","6ae5f91a7047069f","c39b95325fe90269","d874747b5e6b0b03","7652b86372e17298","34d94ccb62820d2d"]]},{"id":"f077e4ea52bd8113","type":"Task-mm","z":"4c1d134ac16b473b","name":"Move FlowHub calls to the backend","info":"Turns out that much of the flowhub stuff never hits the server rather being captured by the `$.ajaxPrefilter` - this needs to change with FlowHub local since there is more logic now and the servers involved can only be reached from the backend (in some cases).\n\n- FlowHubCreateBranch\n- FlowHubPush\n- FlowHubDiff\n- FlowHubPull\n- FlowHubToken\n- FlowHubTokens\n- FlowHubCatalogue\n- FlowHubDiffFrame\n- FlowHubTokenCheck","mkdtemp":false,"sumPass":false,"sumPassPrio":0,"sumPassNodeId":"","createdAt":"2026-10-28T08:14:47.506Z","updatedAt":"2026-10-29T07:53:14.006Z","locked":false,"taskStatus":"done","x":623.1560668945312,"y":1142.45263671875,"wires":[["1579ec8387f78888","9e4a14ef542b346f"]]},{"id":"9e4a14ef542b346f","type":"Task-mm","z":"4c1d134ac16b473b","name":"Store and retreive correct flow revisions between reloads","info":"at the moment the flow revisions are stored correctly and therefore aren;t sent to the server to compare against existing revisions.\n\ntest case:\n\n- create new flow \n- push flow\n- in another NR, pull, change and push the flow\n- back in the original Erlang-Red, change and push and the submission will work \n\npush should fail because the revision used by the erlang red was the old original revision.\n\nthis works with Node-RED.\n","mkdtemp":false,"sumPass":false,"sumPassPrio":0,"sumPassNodeId":"","createdAt":"2026-10-30T08:45:46.078Z","updatedAt":"2026-10-30T09:14:08.065Z","locked":false,"taskStatus":"done","x":1276.9973907470703,"y":604.040952205658,"wires":[[]]},{"id":"9f1418770f9d9217","type":"Task-mm","z":"4c1d134ac16b473b","name":"- FlowHubCreateBranch","info":"- FlowHubCreateBranch","mkdtemp":false,"sumPass":false,"sumPassPrio":0,"sumPassNodeId":"","createdAt":"2026-10-29T07:56:06.303Z","updatedAt":"2026-10-29T07:56:06.303Z","locked":false,"taskStatus":"done","x":1376.7289123535156,"y":1639.7625427246094,"wires":[[]]},{"id":"64ac5e43c2fd068f","type":"Task-mm","z":"4c1d134ac16b473b","name":"- FlowHubPush","info":"- Ensure that force push works\n\nHere the flags have to be respected and correctly assigned.\n\n- Ensure the revision checking is working\n\nThe most recent version of the flow is sent to the backend and needs to be sent on to the server. \n\nThis isn't working in Erlang-Red.\n\n- Ensure the push comments are stored\n\n- Ensure that dates are stored\n","mkdtemp":false,"sumPass":false,"sumPassPrio":0,"sumPassNodeId":"","createdAt":"2026-10-29T07:56:06.311Z","updatedAt":"2026-10-30T08:31:14.285Z","locked":false,"taskStatus":"done","x":1382.599723815918,"y":726.7157397270203,"wires":[["994b29a9187fef70","cca248ed0c864ce4","91e690ca037f75fe","20ee95d786b5b62d","160b8b1d684e30e7"]]},{"id":"8fde532e6320d5e8","type":"Task-mm","z":"4c1d134ac16b473b","name":"- FlowHubDiff","info":"- FlowHubDiff","mkdtemp":false,"sumPass":false,"sumPassPrio":0,"sumPassNodeId":"","createdAt":"2026-10-29T07:56:06.318Z","updatedAt":"2026-10-29T07:56:06.318Z","locked":false,"taskStatus":"done","x":1587.5430450439453,"y":1268.3093905448914,"wires":[["7652b86372e17298"]]},{"id":"2f655018b6bce854","type":"Task-mm","z":"4c1d134ac16b473b","name":"- FlowHubPull","info":"- FlowHubPull\n\nIncluding the revision specification","mkdtemp":false,"sumPass":false,"sumPassPrio":0,"sumPassNodeId":"","createdAt":"2026-10-29T07:56:06.323Z","updatedAt":"2026-10-30T09:12:53.199Z","locked":false,"taskStatus":"done","x":1382.5999908447266,"y":821.5459399223328,"wires":[["1a9c90e7d5f066fd"]]},{"id":"6ae5f91a7047069f","type":"Task-mm","z":"4c1d134ac16b473b","name":"- FlowHubToken","info":"- FlowHubToken","mkdtemp":false,"sumPass":false,"sumPassPrio":0,"sumPassNodeId":"","createdAt":"2026-10-29T07:56:06.329Z","updatedAt":"2026-10-29T07:56:06.329Z","locked":false,"taskStatus":"done","x":1464.7733917236328,"y":1416.1295886039734,"wires":[[]]},{"id":"c39b95325fe90269","type":"Task-mm","z":"4c1d134ac16b473b","name":"- FlowHubTokens","info":"- FlowHubTokens","mkdtemp":false,"sumPass":false,"sumPassPrio":0,"sumPassNodeId":"","createdAt":"2026-10-29T07:56:06.333Z","updatedAt":"2026-10-29T07:56:06.333Z","locked":false,"taskStatus":"done","x":1424.0360794067383,"y":1525.1998615264893,"wires":[["0756c581bc2c42ba","87c53943e8e9064f"]]},{"id":"d874747b5e6b0b03","type":"Task-mm","z":"4c1d134ac16b473b","name":"- FlowHubCatalogue","info":"- FlowHubCatalogue","mkdtemp":false,"sumPass":false,"sumPassPrio":0,"sumPassNodeId":"","createdAt":"2026-10-29T07:56:06.338Z","updatedAt":"2026-10-29T07:56:06.338Z","locked":false,"taskStatus":"done","x":1403.5435791015625,"y":920.8665976524353,"wires":[[]]},{"id":"7652b86372e17298","type":"Task-mm","z":"4c1d134ac16b473b","name":"- FlowHubDiffFrame","info":"- FlowHubDiffFrame","mkdtemp":false,"sumPass":false,"sumPassPrio":0,"sumPassNodeId":"","createdAt":"2026-10-29T07:56:06.343Z","updatedAt":"2026-10-29T07:56:06.343Z","locked":false,"taskStatus":"done","x":1852.736686706543,"y":1212.3051481246948,"wires":[["4e31f852e7ad8e6a"]]},{"id":"34d94ccb62820d2d","type":"Task-mm","z":"4c1d134ac16b473b","name":"- FlowHubTokenCheck","info":"- FlowHubTokenCheck","mkdtemp":false,"sumPass":false,"sumPassPrio":0,"sumPassNodeId":"","createdAt":"2026-10-29T07:56:06.348Z","updatedAt":"2026-10-29T07:56:06.348Z","locked":false,"taskStatus":"done","x":1402.5999908447266,"y":1011.923264503479,"wires":[[]]},{"id":"994b29a9187fef70","type":"Task-mm","z":"4c1d134ac16b473b","name":"Ensure that force push works","info":"- Ensure that force push works\n\nHere the flags have to be respected and correctly assigned.\n","mkdtemp":false,"sumPass":false,"sumPassPrio":0,"sumPassNodeId":"","createdAt":"2026-10-30T08:31:26.769Z","updatedAt":"2026-10-30T08:31:41.722Z","locked":false,"taskStatus":"done","x":1839.5862350463867,"y":660.223804473877,"wires":[[]]},{"id":"cca248ed0c864ce4","type":"Task-mm","z":"4c1d134ac16b473b","name":"Ensure the revision checking is working","info":"- Ensure the revision checking is working\n\nThe most recent version of the flow is sent to the backend and needs to be sent on to the server. \n\nThis isn't working in Erlang-Red.\n","mkdtemp":false,"sumPass":false,"sumPassPrio":0,"sumPassNodeId":"","createdAt":"2026-10-30T08:31:26.785Z","updatedAt":"2026-10-30T08:32:48.967Z","locked":false,"taskStatus":"done","x":1879.5858612060547,"y":752.3008470535278,"wires":[[]]},{"id":"91e690ca037f75fe","type":"Task-mm","z":"4c1d134ac16b473b","name":"Ensure the push comments are stored","info":"- Ensure the push comments are stored\n","mkdtemp":false,"sumPass":false,"sumPassPrio":0,"sumPassNodeId":"","createdAt":"2026-10-30T08:31:26.793Z","updatedAt":"2026-10-30T08:32:23.013Z","locked":false,"taskStatus":"done","x":1867.482234954834,"y":843.6765928268433,"wires":[[]]},{"id":"20ee95d786b5b62d","type":"Task-mm","z":"4c1d134ac16b473b","name":"Ensure that commit dates are stored if provided","info":"- Ensure that commit dates are stored if provided\n","mkdtemp":false,"sumPass":false,"sumPassPrio":0,"sumPassNodeId":"","createdAt":"2026-10-30T08:31:26.801Z","updatedAt":"2026-10-30T08:32:42.195Z","locked":false,"taskStatus":"done","x":1899.5862274169922,"y":935.7536840438843,"wires":[[]]},{"id":"160b8b1d684e30e7","type":"Task-mm","z":"4c1d134ac16b473b","name":"Ensure that force create new flow works","info":"","mkdtemp":false,"sumPass":false,"sumPassPrio":0,"sumPassNodeId":"","createdAt":"2026-10-30T08:31:26.769Z","updatedAt":"2026-10-30T08:32:04.896Z","locked":false,"taskStatus":"done","x":1886.0015716552734,"y":561.5288133621216,"wires":[[]]},{"id":"1a9c90e7d5f066fd","type":"Task-mm","z":"4c1d134ac16b473b","name":"Including the revision specification","info":"Including the revision specification","mkdtemp":false,"sumPass":false,"sumPassPrio":0,"sumPassNodeId":"","createdAt":"2026-10-29T07:56:06.323Z","updatedAt":"2026-10-30T09:13:11.803Z","locked":false,"taskStatus":"done","x":1867.1646575927734,"y":1061.654914855957,"wires":[[]]},{"id":"0756c581bc2c42ba","type":"Task-mm","z":"4c1d134ac16b473b","name":"credentail store has the tokens needs to be retrieved from here","info":"","mkdtemp":false,"sumPass":false,"sumPassPrio":0,"sumPassNodeId":"","createdAt":"2026-10-31T09:20:47.552Z","updatedAt":"2026-10-31T09:21:08.836Z","locked":false,"taskStatus":"done","x":1950.5602645874023,"y":1581.1913204193115,"wires":[[]]},{"id":"87c53943e8e9064f","type":"Task-mm","z":"4c1d134ac16b473b","name":"Store and retrieve the flowhub config node","info":"being stored in the credentials store.\n\n```\nConfig Store #{<<\"381833764272c0d7\">> =>\n #{<<\"apiTokenType\">> => <<\"cred\">>,\n <<\"credentials\">> =>\n #{<<\"apiToken\">> => <<\"empty\">>,\n <<\"tokens\">> =>\n [#{<<\"name\">> => <<\"empty\">>,\n <<\"type\">> => <<\"cred\">>,\n <<\"val\">> => <<\"empty\">>}]},\n <<\"email\">> => <<>>,\n <<\"flowid\">> => <<\"50a059a26df667d2\">>,\n <<\"flowrevision\">> => <<>>,\n <<\"flowrevisions\">> =>\n #{<<\"059f4ad1c62cfeef\">> =>\n <<\"16dc2e2e3521449a5cbd5e4363e3755618dbffdc\">>,\n <<\"0d3dfc0fc42aeb44\">> =>\n <<\"575008a80d74d6b4f79330ac477d5a9e9cb20c54\">>,\n <<\"1195f2f12adf68cb\">> =>\n <<\"0804a22dc5285687d739c71a31189c70d03e1f6a\">>,\n <<\"31d29e27a79b2602\">> =>\n <<\"3981b32171b58d6fc112d81ea8c4e8ef5607bfd1\">>,\n <<\"3358943f92acaaa2\">> =>\n <<\"0169e979438b216bcdbaefd32b29fdcfec2053e9\">>,\n <<\"50a059a26df667d2\">> =>\n <<\"8cdf9061a20f2203a70fa6c05cfeb73b59abac23\">>,\n <<\"74ea134517e51857\">> =>\n <<\"22fd999983a7b6b79fb66a5c6488277e47e771a8\">>,\n <<\"7ee11d3f374b312d\">> =>\n <<\"dcfc5c0a6a7992d5bf01e72f179381287974c9f7\">>,\n <<\"87e40eb4505e7aec\">> =>\n <<\"9be67d859617f3c2323727e54b984e11f9ce0fdb\">>},\n <<\"forcepush\">> => false,<<\"fullname\">> => <<>>,\n <<\"id\">> => <<\"381833764272c0d7\">>,<<\"notab\">> => false,\n <<\"pushcomment\">> => <<>>,<<\"pushnewflows\">> => false,\n <<\"type\">> => <<\"FlowHubCfg\">>},\n <<\"4825147a4f47e0b0\">> =>\n #{<<\"data\">> => <<\"some default value\">>,\n <<\"id\">> => <<\"4825147a4f47e0b0\">>,\n <<\"name\">> => <<\"FlowCompare\">>,\n <<\"type\">> => <<\"FlowCompareCfg\">>},\n <<\"632a21be30c01c03\">> =>\n #{<<\"algorithm\">> => <<\"dagre_lr\">>,\n <<\"id\">> => <<\"632a21be30c01c03\">>,\n <<\"name\">> => <<\"AutoLayout\">>,\n <<\"settings\">> =>\n```","mkdtemp":false,"sumPass":false,"sumPassPrio":0,"sumPassNodeId":"","createdAt":"2026-10-30T12:42:25.116Z","updatedAt":"2026-10-31T09:22:29.840Z","locked":false,"taskStatus":"done","x":1906.4075012207031,"y":1451.9706401824951,"wires":[[]]},{"id":"4e31f852e7ad8e6a","type":"Task-mm","z":"4c1d134ac16b473b","name":"question marks in the compare functionality","info":"Check what is being stored and why the nodes are shown as question marks in the compare.\n\n\n\nReason: ordering of attributes in the JSON object\n\nSolution: doing a AJAX prefilter and including the base64 encoding of the flow data. This is decoded on the backend back to the required object code.\n\nThis ensures that both Erlang-Red and Node-RED send the browser ordered object keys and thus everything is the same in the git store.","mkdtemp":false,"sumPass":false,"sumPassPrio":0,"sumPassNodeId":"","createdAt":"2026-11-01T16:22:34.279Z","updatedAt":"2026-11-02T11:01:57.182Z","locked":false,"taskStatus":"done","x":2185.192939758301,"y":1278.3008279800415,"wires":[[]]},{"id":"8065d860fbafbe1c","type":"Task-mm","z":"4c1d134ac16b473b","name":"store the user settings so that sidebar panells are correct between reloads","info":"store the user settings instead of replying with an empty json\n\n- create a store similar to credential store\n- read the initials settings user or the created one\n","mkdtemp":false,"sumPass":false,"sumPassPrio":0,"sumPassNodeId":"","createdAt":"2026-10-30T08:45:46.078Z","updatedAt":"2026-10-31T15:04:16.587Z","locked":false,"taskStatus":"done","x":701.683837890625,"y":503.8325080871582,"wires":[[]]}]
The difference is that inside Erlang-Red, I can use that to retrieve visual code from a Node-RED instance that is running the GitStore flow. There’s a GitStore flow that is providing the back-end for the version control for storing flow code and doing the comparison visually, and providing a web interface, which is the Webliser interface.
The server code will be ported over to Erlang-Red in a future step so that there’s no need to have a Node-RED installation to have visual version control. But in this initial step, the backed functionality uses Node-RED. The backend functionality does not change when the GitStore flow is running in Erlang-Red, the backend calls are simply accessing an Erlang-Red instance instead.
All commits as part of this update:
Why upgrade the Node-RED editor in the first place? The main reason was the interface, which had improved quite a lot in version 5.
Version 4.0.9:

There is only one configurable side panel here; on the right-hand side is the configurable side panel, and on the left-hand side is the palette with all the nodes, and that’s it. The problem here is that if you have different side panels and plugins for various purposes, (for example, debug logs, message tracing, or view documentation) you end up constantly having to switch between these side panels and plugins. The switcher is at the top right with buttons, and there is also a dropdown once the number of buttons exceeds the displayable range (i.e. beyond six to ten buttons, depending on screen width). There is a dropdown for further plugins, but it is inconvenient if you have many different plugins.
The Node-RED version 5.x interface:

It has four different panels (two on the left and two on the right) which are all configurable. The configuration is at the bottom, where you have groupings; you have four groups of plugins, and these are shown in various plugin cells. I can have documentation open while having the flow explorer open, while having debug open, while having message tracing open—all at the same time. That provides a far better overview and a better way of programming flows.
Shown in the image of the Node-RED 5 interface is, for example, the Explorer on the top left and the FlowHub visual version control on the bottom left. That way, I can always have my version control open and compare my changes to what’s on the server. On the right, I have my message tracing so that I can actually trace messages in live through my flows. At the bottom right, there is a debug panel for any debug messages. All of that can be easily changed with the selection panel at the bottom right, and it’s easy enough to move the various plugins to different locations.
That’s all fully configurable and organisable. That allows one to create an editor for their workflow. I have a created a presenter node which I included in the Erlang-Red editor. The presenter node allows switching these panels to preset configurations. So, if I’m doing debugging, I’ll have a configuration where the panels are set up for debugging. If I’m writing documentation, I’ll have a setup which is ideal for documentation writing. If I’m doing message tracing, I’ll have a preset set of panels to do the message tracing.
That also makes it even more convenient that you can quickly configure your editor for the task you’re doing. All of that is possible in Node-RED 5 with the interface, and it is a far smoother interface than Node-RED 4.
Project plans are completely self-referential, they are visual flow code that I can version to my visual version control system. I had to create a project plan for the overall project, which is visual version controlling for Erlang-Red. This project plan is basically visualised here and allows me to plan my work and my time.
Each task (which is a node) has a colour-coded status: green for done, red for broken, yellow for in progress, and white for not started yet. It’s a very simple project plan tool that I created for Node-RED and Erlang-Red. That way, this tool is also part of the visual version control, so I’m actually also versioning it.
That means I can also create neat animations of how I’m progressing over time. So, that’s all kind of dog-fooding the technology I’m trying to implement for Erlang-Red at the moment!

This text was transcribed from the original audio by AI and then formatted (without altering the text) also by AI. Final polish and images added by a human - i.e. me. All the work described herein was done by me without any explicit AI utilisation.