A helper for organizing Django project settings by relying on well established programming patterns.
Find a file
John R Dietrick cd0f1b4d0c Fix handling of fallback to optparse.OptionParser
By the time the code here runs, it's too late to be modifying
base.BaseCommand.option_list; in fact doing so causes an OptionConflictError if
you later call another management command "recursively" while you're running
the first one.

We want to leave BaseCommand's option_list untouched (it's `()` by default in
Django 1.8+) in case the command we are wrapping has already upgraded to
argparse. BUT, if it hasn't, we'll get an OptionParser back, and can tack our
argument on at the last minute.
2015-12-19 18:25:53 +08:00
configurations Fix handling of fallback to optparse.OptionParser 2015-12-19 18:25:53 +08:00
docs Moved to Jazzband. 2015-12-17 10:22:38 +01:00
test_project Merge remote-tracking branch 'joke2k/dot-env' 2015-01-06 22:34:29 +01:00
tests Travis: use Python 3.5 for Python 3 flake8 test 2015-12-17 23:07:40 +01:00
.coveragerc Simplify coverage setup. 2015-01-06 21:20:52 +01:00
.gitignore Merge remote-tracking branch 'joke2k/dot-env' 2015-01-06 22:34:29 +01:00
.travis.yml Travis: minor: fix indent 2015-12-17 23:31:08 +01:00
AUTHORS Updated authors and license. 2013-04-11 17:14:40 +02:00
CONTRIBUTING.md Moved to Jazzband. 2015-12-17 10:22:38 +01:00
LICENSE Happy New Year! 2014-01-16 19:00:40 +01:00
MANIFEST.in Get rid of manage.py for running tests now that we have django-cadmin. 2015-03-16 15:13:31 +01:00
README.rst Travis: use master branch in build status image 2015-12-17 23:31:08 +01:00
setup.cfg Revert "Use py.test." 2015-02-13 16:43:55 +01:00
setup.py add entrypoints to run in non-source-tree installs 2015-02-19 10:51:32 +01:00
tox.ini Travis/tox: use dj19 tarball, add master; remove unsupported 2015-12-17 23:31:08 +01:00

django-configurations
=====================

.. image:: https://travis-ci.org/jazzband/django-configurations.svg?branch=master
   :alt: Build Status
   :target: https://travis-ci.org/jazzband/django-configurations

.. image:: https://jazzband.co/static/img/badge.svg
   :alt: Jazzband
   :target: https://jazzband.co/

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.

.. __: http://django-configurations.readthedocs.org/en/latest/


Quickstart
----------

Install django-configurations:

.. code-block:: console

    pip install django-configurations

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.::

    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
   :emphasize-lines: 10

    #!/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
   :emphasize-lines: 6

    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.