From 2bfb9edefaac390582be6562a8ab0a4d52912c61 Mon Sep 17 00:00:00 2001 From: Dariusz Choruzy Date: Fri, 18 Sep 2015 02:36:10 +0200 Subject: [PATCH] reformatted settings.rst --- docs/settings.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/settings.rst b/docs/settings.rst index 06a87f3..431263d 100644 --- a/docs/settings.rst +++ b/docs/settings.rst @@ -30,6 +30,6 @@ Django 1.4 has introduced a signed cookie session backend, which stores the whol In this case the Cache-based backend should be used (by setting ``ROSETTA_STORAGE_CLASS = 'rosetta.storage.CacheRosettaStorage'``). Please make sure that a proper ``CACHES`` backend is configured in your Django settings if your Django app is being served in a multi-process environment, or the different server processes, serving subsequent requests, won't find the storage data left by previous requests. -Alternatively you can switch back to using the Session based storage by setting ``ROSETTA_STORAGE_CLASS = 'rosetta.storage.SessionRosettaStorage`` in your settings. This is perfectly safe on Django 1.3. On Django 1.4 or higher make sure you have DON'T use the `signed_cookies `_ ``SESSION_BACKEND`` with this Rosetta storage backend or funky things might happen. +Alternatively you can switch back to using the Session based storage by setting ``ROSETTA_STORAGE_CLASS = 'rosetta.storage.SessionRosettaStorage'`` in your settings. This is perfectly safe on Django 1.3. On Django 1.4 or higher make sure you have DON'T use the `signed_cookies `_ ``SESSION_BACKEND`` with this Rosetta storage backend or funky things might happen. **TL;DR**: if you run Django with gunincorn, mod-wsgi or other multi-process environment, the Django-default ``CACHES`` ``LocMemCache`` backend won't suffice: use memcache instead, or you will run into issues.