mirror of
https://github.com/django/django.git
synced 2025-10-24 06:06:09 +00:00
Refs #36485 -- Rewrapped docs to 79 columns line length.
Lines in the docs files were manually adjusted to conform to the 79 columns limit per line (plus newline), improving readability and consistency across the content.
This commit is contained in:
@@ -40,8 +40,9 @@ For more advanced usage, please read the `Uvicorn documentation <Uvicorn_>`_.
|
||||
Deploying Django using Uvicorn and Gunicorn
|
||||
===========================================
|
||||
|
||||
Gunicorn_ is a robust web server that implements process monitoring and automatic
|
||||
restarts. This can be useful when running Uvicorn in a production environment.
|
||||
Gunicorn_ is a robust web server that implements process monitoring and
|
||||
automatic restarts. This can be useful when running Uvicorn in a production
|
||||
environment.
|
||||
|
||||
To install Uvicorn and Gunicorn, use the following:
|
||||
|
||||
|
||||
@@ -2,10 +2,10 @@
|
||||
How to authenticate against Django's user database from Apache
|
||||
==============================================================
|
||||
|
||||
Since keeping multiple authentication databases in sync is a common problem when
|
||||
dealing with Apache, you can configure Apache to authenticate against Django's
|
||||
:doc:`authentication system </topics/auth/index>` directly. This requires Apache
|
||||
version >= 2.2 and mod_wsgi >= 2.0. For example, you could:
|
||||
Since keeping multiple authentication databases in sync is a common problem
|
||||
when dealing with Apache, you can configure Apache to authenticate against
|
||||
Django's :doc:`authentication system </topics/auth/index>` directly. This
|
||||
requires Apache version >= 2.2 and mod_wsgi >= 2.0. For example, you could:
|
||||
|
||||
* Serve static/media files directly from Apache only to authenticated users.
|
||||
|
||||
|
||||
@@ -37,9 +37,9 @@ deployments.
|
||||
|
||||
WSGI servers obtain the path to the ``application`` callable from their
|
||||
configuration. Django's built-in server, namely the :djadmin:`runserver`
|
||||
command, reads it from the :setting:`WSGI_APPLICATION` setting. By default, it's
|
||||
set to ``<project_name>.wsgi.application``, which points to the ``application``
|
||||
callable in :file:`<project_name>/wsgi.py`.
|
||||
command, reads it from the :setting:`WSGI_APPLICATION` setting. By default,
|
||||
it's set to ``<project_name>.wsgi.application``, which points to the
|
||||
``application`` callable in :file:`<project_name>/wsgi.py`.
|
||||
|
||||
Configuring the settings module
|
||||
===============================
|
||||
|
||||
@@ -124,8 +124,8 @@ use ``WSGIPythonPath``; instead you should use the ``python-path`` option to
|
||||
WSGIProcessGroup example.com
|
||||
|
||||
If you want to serve your project in a subdirectory
|
||||
(``https://example.com/mysite`` in this example), you can add ``WSGIScriptAlias``
|
||||
to the configuration above:
|
||||
(``https://example.com/mysite`` in this example), you can add
|
||||
``WSGIScriptAlias`` to the configuration above:
|
||||
|
||||
.. code-block:: apache
|
||||
|
||||
|
||||
Reference in New Issue
Block a user