This is something I wrote up after playing with the context options. I've filed a PR with some of this added to the Node-RED documentation but thought I'd release it here also. I hope people find it useful. Paul A guide to understanding 'Persistent Context' Prior to Node-RED v0.19.0, data could …

Great write up. I have one question however. When I wish to check on the stored value (file store) the directories under 'context' use obscure node numbering. Would it be possible to use the tab name, (or node name) which is what one might expect to look under? Just a thought. I only care when I…

[image] StrongTown: Would it be possible to use the tab name, (or node name) which is what one might expect to look under? The file store isn't really intended for the user to access directly - its an internal implementation detail. The naming is based on the id of the nodes and flows as they…

[image] tilleul: Also, it's certainly possible to write persistent context to a non-wearable media like a network hard drive or something ? yes, that's what I meant in my reply where I said: use some external storage mechanism (USB hard drive, cloud storage api...).

OK, I understand. Thank you. BTW, I think I read it's not on the list for development however, just for some feedback, I would vote in support of being able to create a utility function somewhere that I can globally call upon in any flow / node rather than repeat code in many function nodes. (NOTE…

Cool! But were do i place this? contextStorage: storeName : { module: "storeModule" } } When i put it in the end before the last } i get an error on starting node-red. Do i understand well that when i put this in settings.js that the global are persistent?

It’s not that it will be policed. Most storage mechanisms only really support serialisable objects, and functions aren’t serialisable. So now we do have persistable context, depending on the storage mechanism, functions (and circular objects) won’t be stored.

[image] zenofmud: contextStorage: storeInFile: { module: "localfilesystem"}, default : { module: "memory" } }, Solved! There was an { missing after contextStorage:

'storeName' and 'storeModule' are the place holder names. Did you look at the examples?

As @zenofmud mentions, he's raised a pull-request to get this integrated into our proper documentation - I'm keen we have good docs that can be linked to for these sorts of questions, rather than rely on linking to forum posts. The pull-request is here: https://github.com/node-red/node-red.github.i…

Node-RED

Node-RED Forum

A guide to understanding 'Persistent Context'

General

tilleul 19 October 2018 17:08 7

Also, it's certainly possible to write persistent context to a non-wearable media like a network hard drive or something ?

Topic		Replies	Views
Problems understanding and implementing Persistent Storage General	42	1342	31 August 2023
🎉 Node-RED 0.19 released News	57	4474	10 January 2019
:question: DISCUSSION: Should nodes save/restore their own context? General	95	4833	19 August 2020
Questions about context saving and something more General	13	362	7 January 2024
Node-red won't start General	63	3749	23 November 2020

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

A guide to understanding 'Persistent Context'

Related topics