A helper for organizing Django project settings by relying on well established programming patterns.
Find a file
Peter Bittner 3c8590a8d4
Merge pull request #222 from jazzband/feature/remove-deprecated-import
Remove deprecated import (gone in Django 1.9)
2018-12-10 13:17:02 +01:00
configurations Remove deprecated import (gone in Django 1.9) 2018-12-10 00:16:51 +01:00
docs Drop heroku from example 2018-10-29 12:47:35 +02:00
test_project Merge remote-tracking branch 'joke2k/dot-env' 2015-01-06 22:34:29 +01:00
tests Also move testing requirements into packaging setup 2018-12-09 15:52:05 +01:00
.gitignore Add sitecustomize.py to fix subprocess coverage reporting 2018-08-16 17:12:37 +02:00
.travis.yml Travis: fix reporting of coverage (#211) 2018-08-30 22:35:13 +02:00
AUTHORS Add extras for optional requirements 2018-12-09 15:48:12 +01:00
CONTRIBUTING.md Typo 2016-03-21 14:40:28 -04:00
LICENSE Happy New Year! 2014-01-16 19:00:40 +01:00
MANIFEST.in included license (#176) 2017-09-23 22:58:44 +02:00
README.rst More badges to display project properties (README) 2018-12-09 18:40:12 +01:00
setup.cfg coverage: track subprocesses 2018-08-16 15:50:41 +02:00
setup.py Also move testing requirements into packaging setup 2018-12-09 15:52:05 +01:00
tox.ini flake8: ignore W503 (and pick W504) (#220) 2018-12-09 18:48:17 +01:00

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://img.shields.io/travis/jazzband/django-configurations/master.svg
   :alt: Build status
   :target: https://travis-ci.org/jazzband/django-configurations
.. |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://readthedocs.org/projects/django-configurations/badge/?version=latest
   :alt: Documentation status
   :target: https://django-configurations.readthedocs.io/en/latest/?badge=latest
.. |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** or **wsgi.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``.

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