search

ioBroker / ioBroker.node-red

Instantiate the server with node-red
Apache License 2.0
52 stars 27 forks source link

Use External NodeRed Instance #124

Open wuast94 opened 3 years ago

wuast94 commented 3 years ago

I have running Node Red in an extra Docker instance and would like to keep it. It should be an option to use and external Nodered instead of hosting one inside iobroker, i like to keep my services on diffrent containers instead of all in one.

Is it possible to make a module in Nodered that connects to iobroker? instead of spawning another nodered in the iobroker container :)

GottZ commented 3 years ago

in regards to this issue: https://github.com/ioBroker/ioBroker.node-red/issues/52

i'd love to see a feature like this too. it would certainly increase maintainability for people who like to twist their own knobs and switches in their tooling.

Apollon77 commented 3 years ago

For me it then feels to mke smore sense to create "ioBroker ndoes" that uses e.g. ws, simple-api or socket.io or such to communicate with an ioBroker instance.

The current nodes rely on the fact that iobroker needs to be installed in a "reachable npm location" to initialize the whole ioBroker DB and connect to it and use a direct connection.

Because if we do that the node-red instance could be on an other host.

SO any developer is open to start building own nodes and use e.g. socket.io to connect to a remote ioBroker instance. The code in the nodes here could be a good basis