A helper for organizing Django project settings by relying on well established programming patterns.
Find a file
2013-11-26 15:46:53 +01:00
configurations Fixed #43 — Removed stdout wrapper from management command hook to not accidently raise an exception too early. Instead use a logger. 2013-11-26 12:25:50 +01:00
docs Minor cleanup. 2013-11-26 15:42:15 +01:00
test_project Ported tests to run via tox and Travis. 2013-11-26 12:25:07 +01:00
tests Fixed a 1.7.x test. 2013-11-26 15:46:53 +01:00
.gitignore Added build dir to ignore list. 2013-04-11 16:04:12 +02:00
.travis.yml Ported tests to run via tox and Travis. 2013-11-26 12:25:07 +01:00
AUTHORS Updated authors and license. 2013-04-11 17:14:40 +02:00
LICENSE Updated authors and license. 2013-04-11 17:14:40 +02:00
manage.py Moved tests out of the configurations packages. 2013-09-09 11:02:43 +02:00
MANIFEST.in Moved the changelog into the docs. 2013-09-19 18:56:07 +02:00
README.rst Moved project templates into cookbooks. 2013-07-27 16:49:50 +02:00
setup.cfg Drop d2to1. 2013-09-09 11:03:00 +02:00
setup.py Drop d2to1. 2013-09-09 11:03:00 +02:00
tox.ini Ported tests to run via tox and Travis. 2013-11-26 12:25:07 +01:00

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

.. image:: https://secure.travis-ci.org/jezdez/django-configurations.png
   :alt: Build Status
   :target: https://travis-ci.org/jezdez/django-configurations

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.

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.