[1.10.x] Fixed #27641 -- Doc'd default local-memory caching in deployment checklist.

Backport of 755406f5ff888e91bacb26f63cbddf7c036793ca from master
This commit is contained in:
Adam Chainz 2016-12-28 19:42:46 -05:00 committed by Tim Graham
parent 3e1be301e2
commit f5e0e15ef8
2 changed files with 4 additions and 1 deletions

View File

@ -103,7 +103,8 @@ default server to return "444 No Response" on an unrecognized host:
----------------- -----------------
If you're using a cache, connection parameters may be different in development If you're using a cache, connection parameters may be different in development
and in production. and in production. Django defaults to per-process :ref:`local-memory caching
<local-memory-caching>` which may not be desirable.
Cache servers often have weak authentication. Make sure they only accept Cache servers often have weak authentication. Make sure they only accept
connections from your application servers. connections from your application servers.

View File

@ -297,6 +297,8 @@ above example, if your server runs as the user ``apache``, make sure the
directory ``/var/tmp/django_cache`` exists and is readable and writable by the directory ``/var/tmp/django_cache`` exists and is readable and writable by the
user ``apache``. user ``apache``.
.. _local-memory-caching:
Local-memory caching Local-memory caching
-------------------- --------------------