I'm experimenting with a idea of making more automation in processes of installing flows. There is couple of topic on forum. But this is something differnt?
otdm - oiyshTerminal deb Manager
ok.
deb as a standard is a known thing. If you have simple flow it's yyy easy to make some script to make some injections to instance.
but if you need dependency's to your flow example python, opencv, not only npm stuff .... why not use something tested?
deb is used for years. by adding one word. you will ask to install on system what you need.
flow
from beginning if you have a system on this thinking process you have a one command:
$ apt install myTurboFlowExample
and if you don't have Node-red it will install it also nodejs if it's not coming as a p rebuild to your distro.
So presumably, you also will need a deb builder so that people can package up Node-RED, required nodes, settings, startup, flow and other files? I would have no idea how to build a deb file.
Also, will you propose to install Node-RED globally or locally? Or give a choice?
@Colin - theoretically why not by changing in concept deb to rpm. About Windows I don't know.
@TotallyInformation - yes with the preparation. If it's a complex flow you need helpers. And it's that. Globally. dpkg is a system operation not users.
Update on the topic. I'm pushing hard.
I went thru clean deb option. Then with otdm-tools as a set of bash helpers. Now I'm on a 0.10 version it's in python now.
I know it's not so in the forum subject. It's python and in update I'm showing action in grafana not Note-red but it's on topic soon...