Option to set the cache lifetime

Caches that are not accessed within the last week will also be evicted.

Along with the usual usage of this package I also use it to only conditionally release my library. For this I cache a version file (Which is automatically bumped on release and contains only the version number) so this action can tell me when it’s changed, because of the hashed keys.

This solution has been really useful and easy to set up, but now a week has passed and I now understand why this job fails.

If for this cache only I could set the lifetime to infinite my problem would be solved.

(Another option would be useful to not litter the cache with these little version files is a maxCaches option, I don’t know if there is an option for that)

[dhadka]

Regardless of my problem, I think options like this would be a nice addition!

Yeah, I actually started a side project during a company hackathon last week that gives users more freedom in how they store and manage files. It has a “time to live” field that would do exactly what you are asking for. It still needs some work, especially on the AWS S3 side, so I wouldn’t recommend it just yet. But it’s open for contributions - https://github.com/dhadka/stockpile

[Phantsure]

@AlexAegis @pbrezina Closing this. This seems like a feature request which currently is not in near scope.