Closed meteoDaniel closed 3 years ago
Dear Daniel,
There should be a flag to enable/disable caching.
I support your suggestion to optionally disable caching at all.
Actually I am not sure if it is possible to switch on/off decorators.
That would not be so easy, right.
So the easiest way would be to set the directory path from outside.
I believe the easiest way would be to use the "memory" backend of dogpile.cache
like we are currently doing on Windows. So, let's just introduce a WD_CACHE_DISABLE
environment variable for that purpose, as suggested by @gutzbenj, see https://github.com/earthobservations/wetterdienst/pull/418#discussion_r617726706? Would you support that way by adjusting your patch #418 accordingly?
Let me know if your time is too scarce to follow up on that. We might support you on giving this patch the finishing touch if you agree on the suggestions.
With kind regards, Andreas.
The implemented caching tries to write data into the
/home/
which is not possible in cloud computing and on machines with restricted write rights.So there should be a flag to enable/disable caching.
A work around could be to use
/tmp
directory which is accesable in AWS Lambda e.g. Another solution could be to have the ability to define the caching directory. But I would prefer to set a flag.Actually I am not sure if it is possible to switch on/off decorators. So the easiest way would be to set the directory path from outside.