You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I'm often doing changes in sites that are not rendered because of the cache.
Cache is very necessary for perfomance but the only solutions that I have now are: waiting 5 minutes or restarting the server.
Describe alternatives you've considered
Reset the thread where the process is running, but I don't know always which POD of the cluster is running.
Additional context
In the saas variant this is not so important because the cache busts when the process is a different one and thus is always breaking the cache for small test sites. The issue becomes more prominent in stratus like sites.
The text was updated successfully, but these errors were encountered:
I think that this is something annoying not just for us, for our clients too. We can implement a simple solution but it has to be automatic and have to work to our SaaS service too.
I will move this issue to prioriticed and we are goint to take it in the following sprints, we can discuss the detail of the implementation in that moment
Is your feature request related to a problem? Please describe.
I'm often doing changes in sites that are not rendered because of the cache.
Cache is very necessary for perfomance but the only solutions that I have now are: waiting 5 minutes or restarting the server.
Describe the solution you'd like
when I have a site like: https://lms.olive.albacore.felipemontoya.co/dashboard
I would like to be able to call: https://lms.olive.albacore.felipemontoya.co/dashboard?eox_tenant=cleancache
or something similar and have the signal process this diferentely at:
https://github.com/eduNEXT/eox-tenant/blob/master/eox_tenant/signals.py#L181
Describe alternatives you've considered
Reset the thread where the process is running, but I don't know always which POD of the cluster is running.
Additional context
In the saas variant this is not so important because the cache busts when the process is a different one and thus is always breaking the cache for small test sites. The issue becomes more prominent in stratus like sites.
The text was updated successfully, but these errors were encountered: