Fixed #27641 -- Doc'd default local-memory caching in deployment checklist.
This commit is contained in:
parent
5cf4894836
commit
755406f5ff
|
@ -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.
|
||||||
|
|
|
@ -302,6 +302,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
|
||||||
--------------------
|
--------------------
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue