Not returning cached value between script calls about cache-manager

[BryanDonovan]

I think this is how the cache-manager-fs store works.. it's per-process as far as I can tell. So each time you run the script, which creates a new process, it also creates a new .dat file.

[BryanDonovan]

In other words, if you have a server running on one process, the caching will work like expected until you restart the server. At that point it will create a new .dat file.

[BryanDonovan]

I haven't tried it myself, but maybe this store would work for multiple processes: https://github.com/sheershoff/node-cache-manager-fs-binary

[Jakobud]

So if I have some external process, like a cronjob that needs to access the cache data and make some changes several times per day, there is no way to do this?

[BryanDonovan]

Yeah, I don't know why the fs file store does it like that (I didn't write it). It seems odd to me, or maybe there's a config option that will let the cache be shared by multiple processes.

[BryanDonovan]

To clarify, if you used the redis store, mongo store, etc. the cache would be shared across processes.

[BryanDonovan]

It happens because of this line:

https://github.com/hotelde/node-cache-manager-fs/blob/master/index.js#L172

You might want to fork that project and submit a pull request with a change that lets you override that uuid part. Basically let you pass in a filename param.

CC @hotelde

[Jakobud]

Thanks for the help. I've been messing with it's code. Some console.log's tell me that it seems to be finding the proper .dat file on startup and it's finding the data, but that data just isn't filled into the cache. Not sure what I'm doing wrong. Thank you for the help,

[Jakobud]

Here is my issue I've opened over there for reference

hotelde/node-cache-manager-fs#9

[BryanDonovan]

No problem.