From 891b0c2041c75b8fb17db488cb14bb7fc5d3decb Mon Sep 17 00:00:00 2001 From: "Nikita P. Shupeyko" Date: Sun, 14 May 2017 16:37:08 +0300 Subject: [PATCH] Fix ALLOWED_HOSTS --- docs/deployment-with-docker.rst | 2 +- docs/settings.rst | 2 ++ 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/deployment-with-docker.rst b/docs/deployment-with-docker.rst index ac4af6e0c..5e8cc89cc 100644 --- a/docs/deployment-with-docker.rst +++ b/docs/deployment-with-docker.rst @@ -53,7 +53,7 @@ It is always better to deploy a site behind HTTPS and will become crucial as the * In the `.env.example`, we have made it simpler for you to change the default `Django Admin` into a custom name through an environmental variable. This should make it harder to guess the access to the admin panel. -* If you are not using a subdomain of the domain name set in the project, then remember to put the your staging/production IP address in the ``ALLOWED_HOSTS``_ environment variable before you deploy your website. Failure to do this will mean you will not have access to your website through the HTTP protocol. +* If you are not using a subdomain of the domain name set in the project, then remember to put the your staging/production IP address in the :code:`DJANGO_ALLOWED_HOSTS` environment variable (see :ref:`settings`) before you deploy your website. Failure to do this will mean you will not have access to your website through the HTTP protocol. * Access to the Django admin is set up by default to require HTTPS in production or once *live*. We recommend that you look into setting up the *Certbot and Let's Encrypt Setup* mentioned below or another HTTPS certification service. diff --git a/docs/settings.rst b/docs/settings.rst index 893a47e90..8b4ad4053 100644 --- a/docs/settings.rst +++ b/docs/settings.rst @@ -1,3 +1,5 @@ +.. _settings: + Settings ==========