Documented misago cache names. #253

docs/developers/cache.rst

@@ -0,0 +1,24 @@
+=============
+Misago Caches
+=============
+
+You can make Misago use its own cache instead of sharing cache with rest of your Django site. To do so, add new cache named ``misago`` to your ``CACHES`` setting::
+
+    CACHES = {
+        'default': {
+            'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache',
+            'LOCATION': '127.0.0.1:11211',
+        },
+        'misago': {
+            'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache',
+            'LOCATION': '127.0.0.1:11212',
+        }
+    }
+
+
+Full-Page Cache
+---------------
+
+By default Full-Page Cache ("FPC") uses same cache other Misago features do, however on active site this may cause your cache backend to frequently delete other still valid caches if it runs out of space.
+
+To avert this, you can define one more cache named ``misago_fpc``.

docs/developers/index.rst

@@ -37,5 +37,6 @@ Following references cover everything you want to know about writing your own ap
    forms
    context_processors
    mails
+   cache
    cache_buster
    thread_store

docs/index.rst

@@ -26,5 +26,6 @@ Table of Contents
    developers/forms
    developers/context_processors
    developers/mails
+   developers/cache
    developers/cache_buster
    developers/thread_store