cookiecutter/cookiecutter-django
1
1
Fork 0
mirror of https://github.com/cookiecutter/cookiecutter-django.git synced 2025-08-06 13:10:17 +03:00
Code Issues Packages Projects Releases Wiki Activity

Fix ALLOWED_HOSTS

Browse Source
This commit is contained in:
Nikita P. Shupeyko 2017-05-14 16:37:08 +03:00
parent 89bc1212b3
commit 891b0c2041
2 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/deployment-with-docker.rst
View File

@ -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.

2
docs/settings.rst
View File

@ -1,3 +1,5 @@
.. _settings:
Settings
==========