2014-06-06 03:46:24 +02:00
==============================
Configuring Django for Wagtail
==============================
2014-07-04 22:57:58 +02:00
To install Wagtail completely from scratch, create a new Django project and an app within that project. For instructions on these tasks, see `Writing your first Django app <https://docs.djangoproject.com/en/dev/intro/tutorial01/> `_ . Your project directory will look like the following::
2014-06-06 03:46:24 +02:00
myproject/
myproject/
__init__.py
settings.py
urls.py
wsgi.py
myapp/
__init__.py
models.py
tests.py
admin.py
views.py
manage.py
2015-05-14 12:29:00 +02:00
From your app directory, you can safely remove `` admin.py `` and `` views.py `` , since Wagtail will provide this functionality for your models. Configuring Django to load Wagtail involves adding modules and variables to `` settings.py `` and URL configuration to `` urls.py `` . For a more complete view of what's defined in these files, see `Django Settings <https://docs.djangoproject.com/en/dev/topics/settings/> `__ and `Django URL Dispatcher <https://docs.djangoproject.com/en/dev/topics/http/urls/> `_ .
2014-06-06 03:46:24 +02:00
What follows is a settings reference which skips many boilerplate Django settings. If you just want to get your Wagtail install up quickly without fussing with settings at the moment, see :ref: `complete_example_config` .
2015-04-19 11:53:34 +02:00
Middleware (`` settings.py `` )
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2014-06-06 03:46:24 +02:00
.. code-block :: python
MIDDLEWARE_CLASSES = (
'django.middleware.common.CommonMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.middleware.csrf.CsrfViewMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'django.contrib.messages.middleware.MessageMiddleware',
'django.middleware.clickjacking.XFrameOptionsMiddleware',
'wagtail.wagtailcore.middleware.SiteMiddleware',
'wagtail.wagtailredirects.middleware.RedirectMiddleware',
)
Wagtail requires several common Django middleware modules to work and cover basic security. Wagtail provides its own middleware to cover these tasks:
`` SiteMiddleware ``
2015-05-28 11:12:48 +02:00
Wagtail routes pre-defined hosts to pages within the Wagtail tree using this middleware.
2014-06-06 03:46:24 +02:00
`` RedirectMiddleware ``
Wagtail provides a simple interface for adding arbitrary redirects to your site and this module makes it happen.
2015-05-14 12:29:00 +02:00
Apps (`` settings.py `` )
~~~~~~~~~~~~~~~~~~~~~~
2014-06-06 03:46:24 +02:00
.. code-block :: python
INSTALLED_APPS = (
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.messages',
'django.contrib.staticfiles',
'compressor',
'taggit',
'modelcluster',
'wagtail.wagtailcore',
'wagtail.wagtailadmin',
'wagtail.wagtaildocs',
'wagtail.wagtailsnippets',
'wagtail.wagtailusers',
'wagtail.wagtailimages',
'wagtail.wagtailembeds',
'wagtail.wagtailsearch',
2015-04-25 19:22:54 +02:00
'wagtail.wagtailsites',
2014-06-06 03:46:24 +02:00
'wagtail.wagtailredirects',
'wagtail.wagtailforms',
'myapp', # your own app
)
Wagtail requires several Django app modules, third-party apps, and defines several apps of its own. Wagtail was built to be modular, so many Wagtail apps can be omitted to suit your needs. Your own app (here `` myapp `` ) is where you define your models, templates, static assets, template tags, and other custom functionality for your site.
Third-Party Apps
----------------
`` compressor ``
Static asset combiner and minifier for Django. Compressor also enables for the use of preprocessors. See `Compressor Documentation`_ .
.. _Compressor Documentation: http://django-compressor.readthedocs.org/en/latest/
`` taggit ``
Tagging framework for Django. This is used internally within Wagtail for image and document tagging and is available for your own models as well. See :ref: `tagging` for a Wagtail model recipe or the `Taggit Documentation`_ .
.. _Taggit Documentation: http://django-taggit.readthedocs.org/en/latest/index.html
`` modelcluster ``
Extension of Django ForeignKey relation functionality, which is used in Wagtail pages for on-the-fly related object creation. For more information, see :ref: `inline_panels` or `the django-modelcluster github project page`_ .
.. _the django-modelcluster github project page: https://github.com/torchbox/django-modelcluster
Wagtail Apps
------------
`` wagtailcore ``
The core functionality of Wagtail, such as the `` Page `` class, the Wagtail tree, and model fields.
`` wagtailadmin ``
The administration interface for Wagtail, including page edit handlers.
`` wagtaildocs ``
The Wagtail document content type.
`` wagtailsnippets ``
Editing interface for non-Page models and objects. See :ref: `Snippets` .
`` wagtailusers ``
User editing interface.
`` wagtailimages ``
The Wagtail image content type.
`` wagtailembeds ``
Module governing oEmbed and Embedly content in Wagtail rich text fields. See :ref: `inserting_videos` .
`` wagtailsearch ``
Search framework for Page content. See :ref: `search` .
`` wagtailredirects ``
2014-08-01 17:49:17 +02:00
Admin interface for creating arbitrary redirects on your site.
2014-06-06 03:46:24 +02:00
`` wagtailforms ``
Models for creating forms on your pages and viewing submissions. See :ref: `form_builder` .
2015-04-19 11:53:34 +02:00
Settings Variables (`` settings.py `` )
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2014-06-06 03:46:24 +02:00
Site Name
---------
.. code-block :: python
WAGTAIL_SITE_NAME = 'Stark Industries Skunkworks'
This is the human-readable name of your Wagtail install which welcomes users upon login to the Wagtail admin.
Search
------
.. code-block :: python
# Override the search results template for wagtailsearch
WAGTAILSEARCH_RESULTS_TEMPLATE = 'myapp/search_results.html'
WAGTAILSEARCH_RESULTS_TEMPLATE_AJAX = 'myapp/includes/search_listing.html'
# Replace the search backend
WAGTAILSEARCH_BACKENDS = {
'default': {
2015-04-30 13:36:24 +02:00
'BACKEND': 'wagtail.wagtailsearch.backends.elasticsearch',
2014-06-06 03:46:24 +02:00
'INDEX': 'myapp'
}
}
2015-04-19 11:53:34 +02:00
The search settings customise the search results templates as well as choosing a custom backend for search. For a full explanation, see :ref: `search` .
2014-06-06 03:46:24 +02:00
Embeds
------
2015-04-25 19:22:54 +02:00
Wagtail uses the oEmbed standard with a large but not comprehensive number of "providers" (Youtube, Vimeo, etc.). You can also use a different embed backend by providing an Embedly key or replacing the embed backend by writing your own embed finder function.
2014-06-06 03:46:24 +02:00
.. code-block :: python
WAGTAILEMBEDS_EMBED_FINDER = 'myapp.embeds.my_embed_finder_function'
Use a custom embed finder function, which takes a URL and returns a dict with metadata and embeddable HTML. Refer to the `` wagtail.wagtailemebds.embeds `` module source for more information and examples.
.. code-block :: python
# not a working key, get your own!
2015-10-07 17:14:15 +02:00
WAGTAILEMBEDS_EMBEDLY_KEY = '253e433d59dc4d2xa266e9e0de0cb830'
2014-06-06 03:46:24 +02:00
Providing an API key for the Embedly service will use that as a embed backend, with a more extensive list of providers, as well as analytics and other features. For more information, see `Embedly`_ .
.. _Embedly: http://embed.ly/
2015-05-14 12:29:00 +02:00
To use Embedly, you must also install their Python module:
2014-06-06 03:46:24 +02:00
2015-10-05 12:07:03 +02:00
.. code-block :: sh
2014-06-06 03:46:24 +02:00
2015-10-05 12:07:03 +02:00
pip install embedly
2014-06-06 03:46:24 +02:00
Images
------
.. code-block :: python
WAGTAILIMAGES_IMAGE_MODEL = 'myapp.MyImage'
This setting lets you provide your own image model for use in Wagtail, which might extend the built-in `` AbstractImage `` class or replace it entirely.
2015-06-15 03:26:54 +02:00
Password Management
-------------------
.. code-block :: python
WAGTAIL_PASSWORD_MANAGEMENT_ENABLED = True
2015-11-18 12:58:19 +01:00
This specifies whether users are allowed to change their passwords (enabled by default).
2015-06-15 03:26:54 +02:00
.. code-block :: python
WAGTAIL_PASSWORD_RESET_ENABLED = True
2015-11-18 12:58:19 +01:00
This specifies whether users are allowed to reset their passwords. Defaults to the same as `` WAGTAIL_PASSWORD_MANAGEMENT_ENABLED `` .
2015-06-15 03:26:54 +02:00
2014-06-06 03:46:24 +02:00
Email Notifications
-------------------
.. code-block :: python
WAGTAILADMIN_NOTIFICATION_FROM_EMAIL = 'wagtail@myhost.io'
2014-06-09 17:47:12 +02:00
Wagtail sends email notifications when content is submitted for moderation, and when the content is accepted or rejected. This setting lets you pick which email address these automatic notifications will come from. If omitted, Django will fall back to using the `` DEFAULT_FROM_EMAIL `` variable if set, and `` webmaster@localhost `` if not.
2014-06-06 03:46:24 +02:00
2015-05-26 15:00:52 +02:00
.. _update_notifications:
2015-04-01 10:23:02 +02:00
Wagtail update notifications
----------------------------
.. code-block :: python
WAGTAIL_ENABLE_UPDATE_CHECK = True
2015-07-15 17:33:34 +02:00
For admins only, Wagtail performs a check on the dashboard to see if newer releases are available. This also provides the Wagtail team with the hostname of your Wagtail site. If you'd rather not receive update notifications, or if you'd like your site to remain unknown, you can disable it with this setting.
2015-04-01 10:23:02 +02:00
2014-07-04 21:51:39 +02:00
Private Pages
-------------
.. code-block :: python
PASSWORD_REQUIRED_TEMPLATE = 'myapp/password_required.html'
This is the path to the Django template which will be used to display the "password required" form when a user accesses a private page. For more details, see the :ref: `private_pages` documentation.
2014-06-06 03:46:24 +02:00
Other Django Settings Used by Wagtail
-------------------------------------
.. code-block :: python
ALLOWED_HOSTS
APPEND_SLASH
AUTH_USER_MODEL
BASE_URL
CACHES
DEFAULT_FROM_EMAIL
INSTALLED_APPS
MEDIA_ROOT
SESSION_COOKIE_DOMAIN
SESSION_COOKIE_NAME
SESSION_COOKIE_PATH
STATIC_URL
TEMPLATE_CONTEXT_PROCESSORS
USE_I18N
2014-07-04 22:57:58 +02:00
For information on what these settings do, see `Django Settings <https://docs.djangoproject.com/en/dev/ref/settings/> `__ .
2014-06-06 03:46:24 +02:00
URL Patterns
------------
.. code-block :: python
from django.contrib import admin
from wagtail.wagtailcore import urls as wagtail_urls
from wagtail.wagtailadmin import urls as wagtailadmin_urls
from wagtail.wagtaildocs import urls as wagtaildocs_urls
2015-03-18 22:46:20 +01:00
from wagtail.wagtailsearch import urls as wagtailsearch_urls
2014-06-06 03:46:24 +02:00
2015-04-02 14:09:02 +02:00
urlpatterns = [
2014-06-06 03:46:24 +02:00
url(r'^django-admin/', include(admin.site.urls)),
url(r'^admin/', include(wagtailadmin_urls)),
2015-03-18 22:46:20 +01:00
url(r'^search/', include(wagtailsearch_urls)),
2014-06-06 03:46:24 +02:00
url(r'^documents/', include(wagtaildocs_urls)),
2015-05-14 12:29:00 +02:00
# Optional URL for including your own vanilla Django urls/views
2014-06-06 03:46:24 +02:00
url(r'', include('myapp.urls')),
# For anything not caught by a more specific rule above, hand over to
# Wagtail's serving mechanism
url(r'', include(wagtail_urls)),
2015-04-02 14:09:02 +02:00
]
2014-06-06 03:46:24 +02:00
This block of code for your project's `` urls.py `` does a few things:
* Load the vanilla Django admin interface to `` /django-admin/ ``
* Load the Wagtail admin and its various apps
2015-05-14 12:29:00 +02:00
* Dispatch any vanilla Django apps you're using other than Wagtail which require their own URL configuration (this is optional, since Wagtail might be all you need)
2014-06-06 03:46:24 +02:00
* Lets Wagtail handle any further URL dispatching.
2015-05-14 12:29:00 +02:00
That's not everything you might want to include in your project's URL configuration, but it's what's necessary for Wagtail to flourish.
2014-06-06 03:46:24 +02:00
.. _complete_example_config:
2015-04-19 11:53:34 +02:00
Ready to Use Example Configuration Files
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2014-06-06 03:46:24 +02:00
These two files should reside in your project directory (`` myproject/myproject/ `` ).
2015-04-19 11:53:34 +02:00
`` settings.py ``
---------------
2014-06-06 03:46:24 +02:00
.. code-block :: python
import os
PROJECT_ROOT = os.path.join(os.path.dirname(__file__), '..', '..')
DEBUG = True
TEMPLATE_DEBUG = DEBUG
ADMINS = (
# ('Your Name', 'your_email@example.com'),
)
MANAGERS = ADMINS
# Default to dummy email backend. Configure dev/production/local backend
# as per https://docs.djangoproject.com/en/dev/topics/email/#email-backends
EMAIL_BACKEND = 'django.core.mail.backends.dummy.EmailBackend'
DATABASES = {
'default': {
'ENGINE': 'django.db.backends.postgresql_psycopg2',
'NAME': 'myprojectdb',
'USER': 'postgres',
'PASSWORD': '',
'HOST': '', # Set to empty string for localhost.
'PORT': '', # Set to empty string for default.
'CONN_MAX_AGE': 600, # number of seconds database connections should persist for
}
}
# Hosts/domain names that are valid for this site; required if DEBUG is False
# See https://docs.djangoproject.com/en/1.5/ref/settings/#allowed-hosts
ALLOWED_HOSTS = []
# Local time zone for this installation. Choices can be found here:
# http://en.wikipedia.org/wiki/List_of_tz_zones_by_name
# although not all choices may be available on all operating systems.
# On Unix systems, a value of None will cause Django to use the same
# timezone as the operating system.
# If running in a Windows environment this must be set to the same as your
# system time zone.
TIME_ZONE = 'Europe/London'
# Language code for this installation. All choices can be found here:
# http://www.i18nguy.com/unicode/language-identifiers.html
LANGUAGE_CODE = 'en-gb'
SITE_ID = 1
# If you set this to False, Django will make some optimizations so as not
# to load the internationalization machinery.
USE_I18N = True
# If you set this to False, Django will not format dates, numbers and
# calendars according to the current locale.
# Note that with this set to True, Wagtail will fall back on using numeric dates
# in date fields, as opposed to 'friendly' dates like "24 Sep 2013", because
# Python's strptime doesn't support localised month names: https://code.djangoproject.com/ticket/13339
USE_L10N = False
# If you set this to False, Django will not use timezone-aware datetimes.
USE_TZ = True
# Absolute filesystem path to the directory that will hold user-uploaded files.
# Example: "/home/media/media.lawrence.com/media/"
MEDIA_ROOT = os.path.join(PROJECT_ROOT, 'media')
# URL that handles the media served from MEDIA_ROOT. Make sure to use a
# trailing slash.
# Examples: "http://media.lawrence.com/media/", "http://example.com/media/"
MEDIA_URL = '/media/'
# Absolute path to the directory static files should be collected to.
# Don't put anything in this directory yourself; store your static files
# in apps' "static/" subdirectories and in STATICFILES_DIRS.
# Example: "/home/media/media.lawrence.com/static/"
STATIC_ROOT = os.path.join(PROJECT_ROOT, 'static')
# URL prefix for static files.
# Example: "http://media.lawrence.com/static/"
STATIC_URL = '/static/'
# List of finder classes that know how to find static files in
# various locations.
STATICFILES_FINDERS = (
'django.contrib.staticfiles.finders.FileSystemFinder',
'django.contrib.staticfiles.finders.AppDirectoriesFinder',
'compressor.finders.CompressorFinder',
)
# Make this unique, and don't share it with anybody.
2014-06-09 17:47:12 +02:00
SECRET_KEY = 'change-me'
2014-06-06 03:46:24 +02:00
# List of callables that know how to import templates from various sources.
TEMPLATE_LOADERS = (
'django.template.loaders.filesystem.Loader',
'django.template.loaders.app_directories.Loader',
)
MIDDLEWARE_CLASSES = (
'django.middleware.common.CommonMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.middleware.csrf.CsrfViewMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'django.contrib.messages.middleware.MessageMiddleware',
'django.middleware.clickjacking.XFrameOptionsMiddleware',
'wagtail.wagtailcore.middleware.SiteMiddleware',
'wagtail.wagtailredirects.middleware.RedirectMiddleware',
)
from django.conf import global_settings
TEMPLATE_CONTEXT_PROCESSORS = global_settings.TEMPLATE_CONTEXT_PROCESSORS + (
'django.core.context_processors.request',
)
ROOT_URLCONF = 'myproject.urls'
# Python dotted path to the WSGI application used by Django's runserver.
WSGI_APPLICATION = 'wagtaildemo.wsgi.application'
INSTALLED_APPS = (
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.messages',
'django.contrib.staticfiles',
'compressor',
'taggit',
'modelcluster',
'wagtail.wagtailcore',
'wagtail.wagtailadmin',
'wagtail.wagtaildocs',
'wagtail.wagtailsnippets',
'wagtail.wagtailusers',
'wagtail.wagtailimages',
'wagtail.wagtailembeds',
'wagtail.wagtailsearch',
'wagtail.wagtailredirects',
'wagtail.wagtailforms',
'myapp',
)
EMAIL_SUBJECT_PREFIX = '[Wagtail] '
INTERNAL_IPS = ('127.0.0.1', '10.0.2.2')
# A sample logging configuration. The only tangible logging
# performed by this configuration is to send an email to
# the site admins on every HTTP 500 error when DEBUG=False.
# See http://docs.djangoproject.com/en/dev/topics/logging for
# more details on how to customize your logging configuration.
LOGGING = {
'version': 1,
'disable_existing_loggers': False,
'filters': {
'require_debug_false': {
'()': 'django.utils.log.RequireDebugFalse'
}
},
'handlers': {
'mail_admins': {
'level': 'ERROR',
'filters': ['require_debug_false'],
'class': 'django.utils.log.AdminEmailHandler'
}
},
'loggers': {
'django.request': {
'handlers': ['mail_admins'],
'level': 'ERROR',
'propagate': True,
},
}
}
# WAGTAIL SETTINGS
# This is the human-readable name of your Wagtail install
# which welcomes users upon login to the Wagtail admin.
WAGTAIL_SITE_NAME = 'My Project'
# Override the search results template for wagtailsearch
# WAGTAILSEARCH_RESULTS_TEMPLATE = 'myapp/search_results.html'
# WAGTAILSEARCH_RESULTS_TEMPLATE_AJAX = 'myapp/includes/search_listing.html'
# Replace the search backend
#WAGTAILSEARCH_BACKENDS = {
# 'default': {
2015-04-30 13:36:24 +02:00
# 'BACKEND': 'wagtail.wagtailsearch.backends.elasticsearch',
2014-06-06 03:46:24 +02:00
# 'INDEX': 'myapp'
# }
#}
# Wagtail email notifications from address
# WAGTAILADMIN_NOTIFICATION_FROM_EMAIL = 'wagtail@myhost.io'
# If you want to use Embedly for embeds, supply a key
# (this key doesn't work, get your own!)
2015-10-07 17:14:15 +02:00
# WAGTAILEMBEDS_EMBEDLY_KEY = '253e433d59dc4d2xa266e9e0de0cb830'
2014-06-06 03:46:24 +02:00
2015-04-19 11:53:34 +02:00
`` urls.py ``
-----------
2014-06-06 03:46:24 +02:00
.. code-block :: python
from django.conf.urls import patterns, include, url
from django.conf.urls.static import static
from django.views.generic.base import RedirectView
from django.contrib import admin
from django.conf import settings
import os.path
from wagtail.wagtailcore import urls as wagtail_urls
from wagtail.wagtailadmin import urls as wagtailadmin_urls
from wagtail.wagtaildocs import urls as wagtaildocs_urls
2015-03-18 22:46:20 +01:00
from wagtail.wagtailsearch import urls as wagtailsearch__urls
2014-06-06 03:46:24 +02:00
urlpatterns = patterns('',
url(r'^django-admin/', include(admin.site.urls)),
url(r'^admin/', include(wagtailadmin_urls)),
2015-03-18 22:46:20 +01:00
url(r'^search/', include(wagtailsearch_urls)),
2014-06-06 03:46:24 +02:00
url(r'^documents/', include(wagtaildocs_urls)),
# For anything not caught by a more specific rule above, hand over to
# Wagtail's serving mechanism
url(r'', include(wagtail_urls)),
)
if settings.DEBUG:
from django.contrib.staticfiles.urls import staticfiles_urlpatterns
urlpatterns += staticfiles_urlpatterns() # tell gunicorn where static files are in dev mode
urlpatterns += static(settings.MEDIA_URL + 'images/', document_root=os.path.join(settings.MEDIA_ROOT, 'images'))
urlpatterns += patterns('',
(r'^favicon\.ico$', RedirectView.as_view(url=settings.STATIC_URL + 'myapp/images/favicon.ico'))
)