Fork

Main reason for the fork is to have django-constance pip installable with
Django 1.4+ compatibility fixes.

Hopefully we can have this fork merged back into the official repository as
soon as possible.

It also adds the option to use a cached version of the config object.
If constance is used in a situation where there are very frequent lookups
(many per second) it is more preferable to use a cached version of the values
that is refreshed ever so often.

Features

Easily migrate your static settings to dynamic settings.

Admin interface to edit the dynamic settings.

Installation

Install from PyPI the backend specific variant of django-constance:

For the (default) Redis backend:

pip install django-constance[redis]

For the database backend:

pip install django-constance[database]

Alternatively – if you’re sure that the dependencies are already
installed – you can also run:

Backends

Constance ships with a bunch of backends that are used to store the
configuration values. By default it uses the Redis backend. To override
the default please set the CONSTANCE_BACKEND setting to the appropriate
dotted path.

Editing

Fire up your admin and you should see a new app called Constance
with MY_SETTINGS_KEY in the Config pseudo model.

By default changing the settings via the admin is only allowed for super users.
But in case you want to use the admin’s ability to implement custom
authorization checks, feel free to set the CONSTANCE_SUPERUSER_ONLY setting
to False and give the users or user groups access to the
constance.change_config permission.