How to transport node-red devs between dev/acc/production environments

General
1

Which files should be synced across environments? It's important that local configurations like connection strings towards external systems are not overwritten.
I have noticed that environmental variables are added in the flow.json file together with the value.
This completely beats the purpose as transporting the flow.json file will reset the values!

So what is the correct approach to make sure the connection details are seperated from the developments itself to ensure easy transport?

2

Can you give a specific example of that? The flows file should not include environment variables.

3

I added the environmental variables on the flow itself. The file starts as such:

{
    "id": "96f135b65dd8f293",
    "type": "tab",
    "label": "Mendix Integration",
    "disabled": false,
    "info": "",
    "env": [
        {
            "name": "MendixURL",
            "value": "http://localhost:8070",
            "type": "str"
        },
        {
            "name": "PlantCode",
            "value": "1000",
            "type": "str"
        },
        {
            "name": "MendixPassword",
            "type": "cred"
        },
        {
            "name": "MendixUsername",
            "value": "ws",
            "type": "str"
        }
    ]
},
4

Well if you don't want them in the flow then don't do it. Specify them in your node red startup script or in the OS system environment.

5

I get that, but the concept of environmental variables is that the values behind the variables are seperated from the process. So either the terminology is out of place when it comes to defining these on flow level, or they should be seperated from the flow file.

6

Not necessarily. Node red provides additional flexibility in this case.

7

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.