Option to replace the Settings.js file from the NodeRed snap

[m3yco]

Hallo ctrlX CORE team,

the Settings.js file has many setting options that could be helpful for the development of NodeRed, for example:

• mqttReconnectTime
• definition an implementation of global context Function
• set enviroment variables for configs
• context Storage parameters to store data globally or persistently in a file
• to declare own logging levels

After the app installation, this file is in the same root / nodered folder structure as the flows.json is located.

My question is could you not make this file replaceable? In the past, this was possible with the pre-series devices.

I have attached a Settings.js file as an example.

Thank you for your efforts and keep up the good work

With best regards

m3yco

[schoeffler]

I have basically the same issue. We need to change the "uiHost" configuration value of NodeRed. The configuration value can be set within the settings.js file. An option to (easily) replace or modify the settings.js would be very helpful to us.

[JohannesA]

Hi all,

this feature will be implemented with next release-milestone RM21.07. 

Stay tuned 🙂 

Best regards

Johannes

[jacaré]

is this feature available and where can I find the documentation?

[CodeShepherd · Accepted solution]

At the moment this info is missing in the documentation. But while booting up the Node-RED snap is looking to following paths in the mentioned order if there is a settings.js ($SNAP_DATA = /var/snap/ctrlx-node-red/current):

1. $SNAP_DATA/solutions/activeConfiguration/node-RED/settings.js
2. $SNAP_DATA/settings.js
3. /snap/ctrlx-node-red/current/settings.js

If you like to change settings you should copy out an original Settings.js already prepared by us for normal usage (otherwise the snap will/could stop working) from the third path, then add your extensions and load it to e.g. the first path to be persistent.

Important notes:

• Changes in the Settings.js file can have unexpected effects (like crashing the app) and will be done on your own risk.
• Getting the original file can only be done with a root user at the moment.
• Beware that the original file probably gets updated in later version of the app so you also will have to adapt your own .js file.

[Yacine]

Hello, 

how could we access to the directory to replace the setting.js file without ssh access ? 

Thanks.

[CodeShepherd]

The first path mentioned above can be accessed via WebDAV. See this post.

[Yacine]

Hi, 

thanks for your feedack, 

the folder accessible with webdav protocol are not complete, 

so for example,  snaps where we can put the settings.js of Node-red is not reachable 

see below for Node-red from webdav

[CodeShepherd]

Sorry for the confusion. The app itself has a direct link to the folder in the app data (activeConfiguration) and the path you can access with WebDAV is linked to the same folder in the file system. WebDAV is limited to only this app data (activeConfiguration) folder and cannot access any other path in the system.

[Yacine]

that means that to insert setting.js file of node-red, we have to use ssh ? 

[CodeShepherd]

No, you do not need ssh. You can use WebDAV and put it to the active configuration (settings.js and data). The app itself can also access to this path.

See this thread for how to write files in Node-RED. Reading is working just the same.

[Yacine]

Hello, 

we tried to load the setting.js file using webDav, but we were not able to load it , see screen.

thanks.

[bigman-node-red]

Thanks Yacine,

Here the Files, for someone who want to test.

You have to install this dependance in NR : https://flows.nodered.org/node/node-red-contrib-fs-ops

You have to change the extention file txt --> json.

Regards.

[Open]

Hello,

I am new to settings.js in node-red, 

I am unable to find settings.js node-red file using WinSCP connection to my ctrlX. Do i have to generate the settings.js file? or i have to have a default settings.js file and copy paste into the ctrlX node-red appdata file directory?

[CodeShepherd]

In my post above I mentioned the paths where the settings.js file is expected. After installation it is only in the installation path available and can be put to the active configuration to be "replaced".

Also as mentioned above: You should copy out an original Settings.js already prepared by us for normal usage (otherwise the snap will/could stop working) from the third path, then add your extensions and load it to e.g. the first path to be persistent.