diff options
| author | Tim Graham <timograham@gmail.com> | 2014-08-26 15:22:08 -0400 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2014-08-26 15:22:28 -0400 |
| commit | 4f0916c374e37ff945f04d7981f3b435eb7cd350 (patch) | |
| tree | 14604246728b1e959b103fceeeea79d4d7088786 | |
| parent | 1b89f976f4919a36c6b70eba428c3a02a94e2822 (diff) | |
[1.7.x] Fixed #21567 -- Documented how to deploy multiple sites using the sites framework.
Backport of 7b9537fb27 from master
| -rw-r--r-- | docs/ref/contrib/sites.txt | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/docs/ref/contrib/sites.txt b/docs/ref/contrib/sites.txt index 618b29e32c..568339a0d1 100644 --- a/docs/ref/contrib/sites.txt +++ b/docs/ref/contrib/sites.txt @@ -272,6 +272,11 @@ will also be created after Django creates the test database. To set the correct name and domain for your project, you can use a :ref:`data migration <data-migrations>`. +In order to serve different sites in production, you'd create a separate +settings file with each ``SITE_ID`` (perhaps importing from a common settings +file to avoid duplicating shared settings) and then specify the appropriate +:envvar:`DJANGO_SETTINGS_MODULE` for each site. + Caching the current ``Site`` object =================================== |