The project template¶
mysite/ home/ migrations/ __init__.py 0001_initial.py 0002_create_homepage.py templates/ home/ home_page.html __init__.py models.py search/ templates/ search/ search.html __init__.py views.py mysite/ settings/ __init__.py base.py dev.py production.py static/ css/ mysite.css js/ mysite.js templates/ 404.html 500.html base.html __init__.py urls.py wsgi.py manage.py requirements.txt
The “home” app¶
This app is here to help get you started quicker by providing a
HomePage model with migrations to create one when you first set up your app.
Default templates and static files¶
The templates directory contains
500.html. These files are very commonly needed on Wagtail sites to they have been added into the template.
The Django settings files are split up into
- This file is for global settings that will be used in both development and production. Aim to keep most of your configuration in this file.
- This file is for settings that will only be used by developers. For example:
DEBUG = True
- This file is for settings that will only run on a production server. For example:
DEBUG = False
This file is used for settings local to a particular machine. This file should never be tracked by a version control system.
On production servers, we recommend that you only store secrets in
local.py(such as API keys and passwords). This can save you headaches in the future if you are ever trying to debug why a server is behaving badly. If you are using multiple servers which need different settings then we recommend that you create a different
production.pyfile for each one.