Cache prefix does not respect main Django settings
girogiro opened this issue · 0 comments
girogiro commented
When singleton model is cached for several instances of Django project into one common backend, each instance needs different cache prefix to prevent cache conflicts. SOLO_CACHE_PREFIX is designed for that, nevertheless it's not read from project's settings but from django-solo package settings where the value is the same for all project instances.