Remote deploy feature issue from the node-red-contrib-flow-manager library

General
1

Hello,

I'm currently testing the remote deploy feature from the Flow Manager library. I've configured the remote URLs as shown below, and Flow Manager is already installed and functioning on the remote destination servers (I can access filters and other functionalities on them without any issues).

However, when attempting a remote deploy to any of the remote servers (e.g., UAT or PPD , Custome_2), I receive a flow error. Interestingly, when I add a custom remote entry that points to the same instance (localhost:1880) as the destination, the deploy works as expected. This suggests the issue may lie with the remote target configuration or a missing setup.

using node red v 4.0.9
Here’s my current flow-manager-cfg.json:

{
  "filter": [],
  "fileFormat": "json",
  "remoteDeploy": {
    "remotes": [
      {
        "name": "UAT",
        "nrAddress": "https://uat-flowbuilder.vas.blueprint.lab/"
      },
      {
        "name": "PPD",
        "nrAddress": "https://ppd-flowbuilder.vas.blueprint.lab"
      },
      {
        "name": "Custom",
        "nrAddress": "http://localhost:1880"
      },
      {
        "name": "Custom_2",
        "nrAddress": "http://localhost:9006" // another locally installed Node-RED instance
      }
    ]
  }
}

image
image917×705 18 KB

image
image819×306 14.5 KB

image
image1493×824 61.7 KB

2

Hey,

:confused::smiling_face_with_tear::smiling_face_with_tear::smiling_face_with_tear::confused::smiling_face_with_tear::smiling_face_with_tear::smiling_face_with_tear::confused::smiling_face_with_tear::smiling_face_with_tear::smiling_face_with_tear:

3

Hi @bereket-09

I'm not sure how widely used the flow manager is or if it's maintainers are active in this forum.

You could consider raising an issue in their repo here: Issues · monogoto.io / node-red-contrib-flow-manager · GitLab - but there doesn't appear to be much activity there either.

4

Hey @knolleary ,

Thanks for your feedback! I’d really appreciate any suggestions you might have on how best to handle this requirement.

To summarize:
I'm trying to set up a development environment where the entire team can freely build and test their flows. However, when it's time to push changes, I want to enforce a remote deployment approach — where developers can select specific tabs/flows to deploy.

Before deployment, I’d like to enable a diff and review process, allowing the team to compare changes and only then accept and push them to the next environment. This way, we can prevent direct access to the UAT and PROD Node-RED instances.

The use case is for a USSD application where each flow represents a different service, and we’re working collaboratively as a team on these flows.