# 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:** 1
**Showing post:** 11

<div class="post-metadata">

### Author: ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@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")

</div>

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

---

_[View the full topic](https://discourse.nodered.org/t/reload-global-variables-after-deploy-restart/135)._