From 755406f5ff888e91bacb26f63cbddf7c036793ca Mon Sep 17 00:00:00 2001 From: Adam Chainz Date: Wed, 28 Dec 2016 19:42:46 -0500 Subject: [PATCH] Fixed #27641 -- Doc'd default local-memory caching in deployment checklist. --- docs/howto/deployment/checklist.txt | 3 ++- docs/topics/cache.txt | 2 ++ 2 files changed, 4 insertions(+), 1 deletion(-) 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 +` 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 9683a44931..fc10025ce5 100644 --- a/docs/topics/cache.txt +++ b/docs/topics/cache.txt @@ -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 user ``apache``. +.. _local-memory-caching: + Local-memory caching --------------------