A helper for organizing Django project settings by relying on well established programming patterns.
Find a file
2014-01-16 17:55:52 +01:00
configurations Fixed #49 -- Added AUTHORS file to package manifest. 2014-01-16 17:53:39 +01:00
docs Fixed README example to not confuse beginners. Thanks, @peterbe. 2013-05-15 12:29:25 +02:00
requirements Initial version. 2012-07-21 15:56:04 +02:00
test_project Made testproject manage.py executable to save my sanity. 2013-04-11 16:04:03 +02:00
.gitignore Added build dir to ignore list. 2013-04-11 16:04:12 +02:00
.travis.yml Bumped up the Django requirement a notch. 2013-04-26 09:03:47 +02:00
AUTHORS Updated authors and license. 2013-04-11 17:14:40 +02:00
CHANGES.rst Updated changelog. 2014-01-16 17:55:52 +01:00
LICENSE Updated authors and license. 2013-04-11 17:14:40 +02:00
Makefile Create wheel by default. 2013-03-28 10:59:12 +01:00
manage.py Initial version. 2012-07-21 15:56:04 +02:00
MANIFEST.in Fixed #49 -- Added AUTHORS file to package manifest. 2014-01-16 17:53:39 +01:00
README.rst Fixed README example to not confuse beginners. Thanks, @peterbe. 2013-05-15 12:29:25 +02:00
setup.cfg Fixed version in setup.cfg, too. 2014-01-16 17:55:44 +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://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 Dev(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=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

    #!/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 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', '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.