A helper for organizing Django project settings by relying on well established programming patterns.
Find a file
2013-03-27 15:34:33 +01:00
configurations Bumped version up a notch. 2013-03-27 15:30:32 +01:00
docs Mention a work around for Celery. Fixes #11. 2013-03-27 15:34:33 +01:00
requirements Initial version. 2012-07-21 15:56:04 +02:00
test_project Added the simple test project. 2013-03-27 11:59:59 +01:00
.gitignore Use d2to1. 2013-03-27 15:30:04 +01:00
.travis.yml Use a matrix to prevent Python 3 and Django < 1.5 tests. 2013-03-27 12:19:11 +01:00
AUTHORS Updated author list. 2012-09-21 20:54:35 +02:00
CHANGES.rst Updated changelog. 2013-03-27 15:29:54 +01:00
LICENSE Added forgotten files (authors and license). 2012-07-21 17:52:05 +02:00
Makefile phony make targets 2012-09-21 15:49:08 +02:00
manage.py Initial version. 2012-07-21 15:56:04 +02:00
MANIFEST.in Add Makefile to sdist. 2013-03-27 15:30:14 +01:00
README.rst Added a note about the new command line option to the readme. 2012-09-21 20:54:58 +02:00
setup.cfg Use d2to1. 2013-03-27 15:30:04 +01:00
setup.py Use d2to1. 2013-03-27 15:30:04 +01:00

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

.. image:: https://secure.travis-ci.org/jezdez/django-configurations.png
   :alt: Build Status
   :target: https://secure.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.Settings`` 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 Settings

    class MySiteSettings(Settings):
        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=MySiteSettings

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=MySiteSettings

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', 'MySiteSettings')

        from configurations.management import execute_from_command_line

        execute_from_command_line(sys.argv)

Notice in line 9 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', 'MySiteSettings')

    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.