Hallo ctrlX CORE team,
the Settings.js file has many setting options that could be helpful for the development of NodeRed, for example:
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
Solved! Go to 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):
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.
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.
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.
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.
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.