I’ve had difficulty accessing, from the Node-RED editor/GUI page, new resources that I’ve Sent to Server. The dropdown lists in the nodes don’t show the new resources. I’ve had to drag a new node in, to see new resources, and then delete the original node.
And today, a resource (a data map) that I know has been sent to the server, because I had been testing with it last week, gave me a “not found” error today. I had to re-send to server for it to reappear.
What is the best practice for “refreshing” the Connect Resources in the various nodes that use them?
That would be very bad, wouldn’t it? I’d understood that the Cleanup Service was to remove UNUSED data sets, and items from the filestore. If it’s removing resources that are used within the “active configuration” (for lack of knowing the proper Node-RED term for active flows), then that’s an issue!
It depends on how resources are send to the server. When using the Designer they are so called Permanent resources. These are not affected by the cleanup service.
Design time I use Send to Server from OL Connect Designer, for my running projects I use a startup flow which uploads resources automatically when deploying the flow. This flow is found in the samples shipped with our nodes. To import the sample:
Choose Import in the Node-RED (hamburger icon in the upper right corner of the editor)
Select Examples
Navigate to: Exmamples > flows > @objectif-lune/node-red-contrib-connect > common patterns > startup flows > 01 - Deploy OL Connect resources
The flow uses an Inject node which triggers the flow on deployment. It uses folder listing of my project folder and subsequently uploads the files found to OL Connect’s File Store.
