Metadata-Version: 2.1
Name: django-configurations
Version: 2.3.1
Summary: A helper for organizing Django settings.
Home-page: https://django-configurations.readthedocs.io/
Author: Jannis Leidel
Author-email: jannis@leidel.info
License: BSD
Platform: UNKNOWN
Classifier: Development Status :: 5 - Production/Stable
Classifier: Framework :: Django
Classifier: Framework :: Django :: 2.2
Classifier: Framework :: Django :: 3.1
Classifier: Framework :: Django :: 3.2
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: BSD License
Classifier: Operating System :: OS Independent
Classifier: Programming Language :: Python
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.6
Classifier: Programming Language :: Python :: 3.7
Classifier: Programming Language :: Python :: 3.8
Classifier: Programming Language :: Python :: 3.9
Classifier: Programming Language :: Python :: 3.10
Classifier: Programming Language :: Python :: Implementation :: PyPy
Classifier: Topic :: Utilities
Requires-Python: >=3.6, <4.0
Description-Content-Type: text/x-rst
Provides-Extra: cache
Provides-Extra: database
Provides-Extra: email
Provides-Extra: search
Provides-Extra: testing
License-File: LICENSE
License-File: AUTHORS

django-configurations |latest-version|
======================================

|build-status| |codecov| |docs| |python-support| |jazzband|

django-configurations eases Django project configuration by relying
on the composability of Python classes. It extends the notion of
Django's module based settings loading with well established
object oriented programming patterns.

Check out the `documentation`_ for more complete examples.

.. |latest-version| image:: https://img.shields.io/pypi/v/django-configurations.svg
   :alt: Latest version on PyPI
   :target: https://pypi.python.org/pypi/django-configurations
.. |build-status| image:: https://github.com/jazzband/django-configurations/workflows/Test/badge.svg
   :target: https://github.com/jazzband/django-configurations/actions
   :alt: GitHub Actions
.. |codecov| image:: https://codecov.io/github/jazzband/django-configurations/coverage.svg?branch=master
   :alt: Codecov
   :target: https://codecov.io/github/jazzband/django-configurations?branch=master
.. |docs| image:: https://img.shields.io/readthedocs/django-configurations/latest.svg
   :alt: Documentation status
   :target: https://readthedocs.org/projects/django-configurations/
.. |python-support| image:: https://img.shields.io/pypi/pyversions/django-configurations.svg
   :target: https://pypi.python.org/pypi/django-configurations
   :alt: Python versions
.. |jazzband| image:: https://jazzband.co/static/img/badge.svg
   :alt: Jazzband
   :target: https://jazzband.co/
.. _documentation: https://django-configurations.readthedocs.io/en/latest/

Quickstart
----------

Install django-configurations:

.. code-block:: console

    pip install django-configurations

or, alternatively, if you want to use URL-based values:

.. code-block:: console

    pip install django-configurations[cache,database,email,search]

Then subclass the included ``configurations.Configuration`` class in your
project's **settings.py** or any other module you're using to store the
settings constants, e.g.:

.. code-block:: python

    # mysite/settings.py

    from configurations import Configuration

    class Dev(Configuration):
        DEBUG = True

Set the ``DJANGO_CONFIGURATION`` environment variable to the name of the class
you just created, e.g. in bash:

.. code-block:: console

    export DJANGO_CONFIGURATION=Dev

and the ``DJANGO_SETTINGS_MODULE`` environment variable to the module
import path as usual, e.g. in bash:

.. code-block:: console

    export DJANGO_SETTINGS_MODULE=mysite.settings

*Alternatively* supply the ``--configuration`` option when using Django
management commands along the lines of Django's default ``--settings``
command line option, e.g.

.. code-block:: console

    python manage.py runserver --settings=mysite.settings --configuration=Dev

To enable Django to use your configuration you now have to modify your
**manage.py**, **wsgi.py** or **asgi.py** script to use django-configurations's versions
of the appropriate starter functions, e.g. a typical **manage.py** using
django-configurations would look like this:

.. code-block:: python

    #!/usr/bin/env python

    import os
    import sys

    if __name__ == "__main__":
        os.environ.setdefault('DJANGO_SETTINGS_MODULE', 'mysite.settings')
        os.environ.setdefault('DJANGO_CONFIGURATION', 'Dev')

        from configurations.management import execute_from_command_line

        execute_from_command_line(sys.argv)

Notice in line 10 we don't use the common tool
``django.core.management.execute_from_command_line`` but instead
``configurations.management.execute_from_command_line``.

The same applies to your **wsgi.py** file, e.g.:

.. code-block:: python

    import os

    os.environ.setdefault('DJANGO_SETTINGS_MODULE', 'mysite.settings')
    os.environ.setdefault('DJANGO_CONFIGURATION', 'Dev')

    from configurations.wsgi import get_wsgi_application

    application = get_wsgi_application()

Here we don't use the default ``django.core.wsgi.get_wsgi_application``
function but instead ``configurations.wsgi.get_wsgi_application``.

Or if you are not serving your app via WSGI but ASGI instead, you need to modify your **asgi.py** file too.:

.. code-block:: python

    import os

    os.environ.setdefault('DJANGO_SETTINGS_MODULE', 'mysite.settings')
    os.environ.setdefault('DJANGO_CONFIGURATION', 'DEV')

    from configurations.asgi import get_asgi_application

    application = get_asgi_application()

That's it! You can now use your project with ``manage.py`` and your favorite
WSGI/ASGI enabled server.


