# Reload global variables after deploy/restart
**URL:** https://discourse.nodered.org/t/reload-global-variables-after-deploy-restart/135
**Category:** Core Development
**Created:** [13 May 2018 01:56 UTC](https://discourse.nodered.org/t/reload-global-variables-after-deploy-restart/135 "2018-05-13T01:56:56Z")
**Posts on this page:** 11
**Page:** 1
### Author:  [@davidcgu](https://discourse.nodered.org/u/davidcgu)
#### Post date: [13 May 2018 01:56 UTC](https://discourse.nodered.org/t/reload-global-variables-after-deploy-restart/135/1 "2018-05-13T01:56:56Z")
If I understood well this is the place where we can make some improvement request right?
If I’m right I think a huge amount of people will be interested that node red has native capability to recover all global variables after deploy/restart.
This will be great and will release the job to be making tricks with MQTT or saving variable by variable to a file etc…
Thanks in advnace
---
### Author:  [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [13 May 2018 07:09 UTC](https://discourse.nodered.org/t/reload-global-variables-after-deploy-restart/135/2 "2018-05-13T07:09:11Z")
Hi @davidcgu
Persistable Context is already on the roadmap and in fact we already have a pull request that implements it for the 0.19 release.
Nick
---
### Author:  [@yesdred](https://discourse.nodered.org/u/yesdred)
#### Post date: [15 May 2018 18:41 UTC](https://discourse.nodered.org/t/reload-global-variables-after-deploy-restart/135/3 "2018-05-15T18:41:19Z")
Perfect. My idea was to ‘store’ variable contents in a retained message and use an Inject node at start to subscribe to the storage topic and store the value again. I was going to ask how best to accomplish this (subscribe in a function, get the payload once, store it in a variable and kill the subscription) but now I rather wait for 0.19.
---
### Author:  [@yesdred](https://discourse.nodered.org/u/yesdred)
#### Post date: [18 May 2018 10:43 UTC](https://discourse.nodered.org/t/reload-global-variables-after-deploy-restart/135/4 "2018-05-18T10:43:41Z")
I looked at the PR. If I understand it correctly, variables are persisted by writing their content to files. I wonder if this better for the hardware (e.g. a Raspberry Pi’s SD card) than retained messages (which are stored also in the file system in a database).
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [18 May 2018 13:27 UTC](https://discourse.nodered.org/t/reload-global-variables-after-deploy-restart/135/5 "2018-05-18T13:27:15Z")
Mosquitto’s database is a simple file DB anyway. File handling is generally very efficient these days and you really don’t see much benefit from a managed DB until you are able to keep indexes fully in memory - not a lot of benefit when the purpose is to reload to memory anyway.
---
### Author:  [@GiovanniG](https://discourse.nodered.org/u/GiovanniG)
#### Post date: [28 January 2019 11:29 UTC](https://discourse.nodered.org/t/reload-global-variables-after-deploy-restart/135/6 "2019-01-28T11:29:19Z")
I have the opposite problem, I need to send some data to hardware to initialize it at every deploy, I?m using a global variable that if undefined will be "0" and at every single event generated by a cyclic Inject increase its value till the data is finished, in my case after 10 data sent cycles, than the main flow can use the hardware if 10 is riched, not before.
WHen I deploy the valuse is already 10.. how can I force it to zero? Thank you
---
### Author:  [@cflurin](https://discourse.nodered.org/u/cflurin)
#### Post date: [28 January 2019 11:56 UTC](https://discourse.nodered.org/t/reload-global-variables-after-deploy-restart/135/7 "2019-01-28T11:56:39Z")
> [@GiovanniG](#):
>
> WHen I deploy the valuse is already 10.. how can I force it to zero? Thank you
I could use an inject node (select `Inject once`) and wire it to a change node that set the global variable to 0;
---
### Author:  [@GiovanniG](https://discourse.nodered.org/u/GiovanniG)
#### Post date: [28 January 2019 11:58 UTC](https://discourse.nodered.org/t/reload-global-variables-after-deploy-restart/135/8 "2019-01-28T11:58:44Z")
Thank you for kind reply, I solved used "contribute config" module and I set there the variable to 0..
---
### Author:  [@ukmoose](https://discourse.nodered.org/u/ukmoose)
#### Post date: [28 January 2019 12:16 UTC](https://discourse.nodered.org/t/reload-global-variables-after-deploy-restart/135/9 "2019-01-28T12:16:32Z")
The default for context is still to use memory which doesn't survive restarts.
So what you can do is to define that for that variable you want to use memory connect store
eg
```auto
flow.set("count", 123, storeName);
```
see [https://nodered.org/docs/writing-functions#storing-data](https://nodered.org/docs/writing-functions#storing-data)
---
### Author:  [@GiovanniG](https://discourse.nodered.org/u/GiovanniG)
#### Post date: [28 January 2019 12:22 UTC](https://discourse.nodered.org/t/reload-global-variables-after-deploy-restart/135/10 "2019-01-28T12:22:16Z")
Then Global will persist but context and flow will be reset on every deploy?
---
### Author:  [@ukmoose](https://discourse.nodered.org/u/ukmoose)
#### Post date: [28 January 2019 12:36 UTC](https://discourse.nodered.org/t/reload-global-variables-after-deploy-restart/135/11 "2019-01-28T12:36:12Z")
See
> [@tada Node-RED 0.19 released](https://discourse.nodered.org/t/node-red-0-19-released/2267/23):
>
> @Paul-Reed @TotallyInformation you configure multiple stores by having multiple configs listed: contextStorage: { default: { module: "localfilesystem" }, memoryOnly: { module: "memory" } }, Then, [as per the docs](https://nodered.org/docs/writing-functions#multiple-context-stores) you can use either default or memoryOnly as the store name argument of context.get/set. Also, once you have multiple stores configured, the TypedInput has an extra drop-down to pick the store to use. Will update the docs.
If you define a memory only context store, you can write specific data to that which will be flushed by a restart, where as other data is written to the default which if you have defined it is saved to the localfilesystem and survives a restart