Hello,
A similar question has been asked in the past... Just want to check if there are some recent changes I may have missed.
I would like to share flows that require contrib nodes to work.
Importing the flows in a docker installation requires very limited knowledge of NodeRed.
Start the container, import flows, deploy. Easy.
Things become a bit more complex when contrib nodes are required.
There might be similar ones (eg. for influxdb two contrib nodes with similar names). And the "importer" (the person importing the flows) has to use the right ones.
I wonder if there is a way to make the life of the "importer" easier.
After importing the flows, an easy way to update the palette.
Thanks.
1 Like
I don't know how everyone else feels about it, but when I share a flow I always try to list the contrib nodes I used to make life easier for whomever is importing it. Unfortunately, not everyone does that.
1 Like
This is what I do in the help I am providing.
However, saying install eg. node-red-contrib-influxdb is not as simple as having an equivalent of the "import" for flows.
Ideally, I'd like to be able to "import" X contrib nodes easily.
The project feature allows that. But, AFAIK, the simple sharing mechanism doesn't.
1 Like
Oh I completely agree that would be quite helpful. When I first got into Node-Red I learned a lot from importing other people's flows. But the lack of information about the contrib nodes made it extremely confusing in the beginning. Now it's more annoying. That would indeed be a cool feature.
1 Like
This topic is definitely on my radar and one we want to address in the near future. Don't have anything more concrete to share right now, but we'll get there.
3 Likes
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
