Node RED VS node-red-docker

Good question.

I expect that we're moving into a phase of AIs talking to AIs, and initially it'll be wasteful (because it'll be mostly English), but eventually, they'll derive their own language and seamlessly upgrade protocols when they determine they're talking to an AI. No clue how that will come about or what that language will look like, but honestly, it's kind of exciting.

Really interesting to think about how they might handle context, as well. Even though we have much bigger context windows (and they'll only get larger), context management is still a resource-management issue, which we'll probably continue to refine, as well. Imagine different strategies for managing both what is brought into the context of each request, as well as what form it could take (level of detail, additional references or commentary on it, etc). Things could get really unreadable even in English, and still be very interpretable for an LLM.

W.r.t. the graph-oriented interfaces, are you thinking something like Node-RED [1]? I'm seeing more and more people mention having LLMs produce non-text or structured outputs, like JSON, UI, and other things. Easy to imagine an LLM that wires together various open-source platforms, on-demand. Something like Node-RED for pipelines/functions, some UI tools for visualization/interactivity, other platforms for messaging, etc...

[1] https://nodered.org/

I skipped to chapter 9 in the article ("Clogged"), and it looked like Pipes failed because it didn't have a large enough team or a well-defined mission. As a result they couldn't offer a super robust product that would lure in enterprise users. "You could not purchase some number of guaranteed-to-work Pipes calls per month" is the quote from the article.

The reason I think that interesting is because that's the model these days for everything from AI tokens to Monday.com seats. It makes me feel like Pipes was before its time.

That said I've been collecting different "business glue" products that are similar to Pipes. To me, like you say, they aren't as interesting, exciting and intuitive as Pipes was, but maybe it just takes a little more digging. I tried to focus on open source tools but some aren't.

- n8n io: https://n8n.io/integrations/mondaycom/

- Node-RED: https://nodered.org/ (just read about this one in this thread)

- trigger dev: trigger.dev

- automatisch.io: https://automatisch.io/docs/

- Activepieces: https://www.activepieces.com/docs/getting-started/introducti...

- Huginn: https://github.com/huginn/huginn

- budibase: https://budibase.com/

- windmill: https://www.windmill.dev/

- tooljet: https://www.tooljet.com/workflows

- Bracket: https://www.usebracket.com/pricing (just SalesForce <-> PostgreSQL)

- Zapier: zapier.com/

Anyway I hope some of these are fun!

Source: https://github.com/node-red/node-red

I believe Node-RED (https://nodered.org/) the way to go. It's just an NPM package to install and you can run it how ever you wish (even on Windows). It has a friendly and helpful community with even the main developers tirelessly answering even beginner level questions. In fact the community forum its THE friendliest forum I've ever been a member of by a large margin. Node-RED's development is supported by the JS Foundation and it's completely free and open source. It's widely used in the industrial automation industry and even integrated by some PLC manufacturers such as Siemens.

Does anyone know if their are plans to implement something like this (or if there are already custom nodes out there). I'd like to experiment with things like looping and incrementing values (like a for loop) for a Ksampler for example. It's only an example though, so I am not looking for a ksampler specific solution; just a generic way to have a variable (e.g. Seed value), run some nodes that use that value, increment the value, and then loop back to the beginning until some sort of condition is met. Node-Red (an event driven node based programming language) has this functionality so it could defintely work in a node based environment such as ComfyUI (see here).

Feb 14 16:16:31 podhost podman\3483]: 2023-02-14 16:16:31.053466474 -0300 -03 m=+0.071815344 container health_status 2177a7448029695a17a9c0c774b8f48875bda76f6bf6e100254532765c6005d7 ()image=docker.io/nodered/node-red:3.0.2-18, name=nodered, health\status=unhealthy, org.label-schema.build-date=2022-08-04T13:19:34Z, org.label-schema.docker.dockerfile=.docker/Dockerfile.alpine, org.label-schema.vcs-type=Git, org.label-schema.license=Apache-2.0, org.label-schema.name=Node-RED, authors=Dave Conway-Jones, Nick O'Leary, James Thomas, Raymond Mouthaan, org.label-schema.vcs-url=https://github.com/node-red/node-red-docker, org.label-schema.version=3.0.2, org.label-schema.arch=, org.label-schema.description=Low-code programming for event-driven applications., org.label-schema.url=https://nodered.org, org.label-schema.vcs-ref=))

I found that Nick O'Leary (founder of Node-RED and the great guy that he is..) already did some research on this, I just had to bring this all together.

I don't use node-red, but I guess they use the node-red user in shell and overriding the process owner causes some issues with that. You can add an issue to their repository if you want.

Standard practice with Node-Red lets the user add dedicated flows and dependencies via the npm install command-line. However within the Node-Red-Docker Repo Wiki, you can also add these flows/dependencies via a dedicated package.json.

# https://nodered.org/docs/getting-started/docker # https://community.home-assistant.io/t/node-red-get-homeassistant-error/53923 node-red: container_name: node-red depends_on: homeassistant: condition: service_started environment: PGID: $PGID PUID: $PUID TZ: $TZ image: nodered/node-red networks: smarthome: ipv4_address: 172.18.0.2 restart: always # https://github.com/node-red/node-red-docker/wiki/Permissions-and-Persistence # chown volume after first run volumes: - $USERDIR2/node-red:/data

Node Red - Flow programming, mainly for IOT