diff options
author | Adam Chainz <me@adamj.eu> | 2016-12-28 19:42:46 -0500 |
---|---|---|
committer | Tim Graham <timograham@gmail.com> | 2016-12-28 19:43:28 -0500 |
commit | f5e0e15ef893a6cca69dbea2da043cc751b60739 (patch) | |
tree | f560c0a8ec08e5b483fec82e0ee3a94565dcbd9d | |
parent | 3e1be301e286b38a4f4f03c3030cae92b1153361 (diff) | |
download | django-f5e0e15ef893a6cca69dbea2da043cc751b60739.tar.gz |
[1.10.x] Fixed #27641 -- Doc'd default local-memory caching in deployment checklist.
Backport of 755406f5ff888e91bacb26f63cbddf7c036793ca from master
-rw-r--r-- | docs/howto/deployment/checklist.txt | 3 | ||||
-rw-r--r-- | docs/topics/cache.txt | 2 |
2 files changed, 4 insertions, 1 deletions
diff --git a/docs/howto/deployment/checklist.txt b/docs/howto/deployment/checklist.txt index 4eec185ad9..8d7c27b04f 100644 --- a/docs/howto/deployment/checklist.txt +++ b/docs/howto/deployment/checklist.txt @@ -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 -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 connections from your application servers. diff --git a/docs/topics/cache.txt b/docs/topics/cache.txt index 12f27c2db6..dc35c10821 100644 --- a/docs/topics/cache.txt +++ b/docs/topics/cache.txt @@ -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 user ``apache``. +.. _local-memory-caching: + Local-memory caching -------------------- |