django-livesettings / docs / usage.rst


A very simple example project is in the directory :file:`livesettings/test_app`. It is almost identical to the following description and is a useful example for integrating livesettings into your app.


In order to use livesettings, you will need to create a :file:`` in your django application. For this example, we will create a :file:`` file in the 'myapp' directory.

For this specific app, we want to allow an admin user to control how many images are displayed on the front page of our site. We will create the following :file:``:

from livesettings import config_register, ConfigurationGroup, PositiveIntegerValue, MultipleStringValue
from django.utils.translation import ugettext_lazy as _

# First, setup a grup to hold all our possible configs
MYAPP_GROUP = ConfigurationGroup(
    'MyApp',               # key: internal name of the group to be created
    _('My App Settings'),  # name: verbose name which can be automatically translated
    ordering=0             # ordering: order of group in the list (default is 1)

# Now, add our number of images to display value
# If a user doesn't enter a value, default to 5
    MYAPP_GROUP,           # group: object of ConfigurationGroup created above
        'NUM_IMAGES',      # key:   internal name of the configuration value to be created
        description = _('Number of images to display'),              # label for the value
        help_text = _("How many images to display on front page."),  # help text
        default = 5        # value used if it have not been modified by the user interface

# Another example of allowing the user to select from several values
        description=_("Measurement System"),
        help_text=_("Default measurement system to use."),

In order to activate this file, add the following line to your :file:``:

import config

You can now see the results of your work by running the dev server and going to settings

python runserver

Dislayed values can be limited to only one group if you display group settings :: where MyApp is the key name of the displayed group.

Accessing your value in a view

Now that you have been able to set a value and allow a user to change it, the next step is to access it from a view.

In a :file:``, you can use the config_value function to get access to the value. Here is a very simple view that passes the value to your template:

from django.shortcuts import render_to_response
from livesettings import config_value

def index(request):
    image_count = config_value('MyApp','NUM_IMAGES')
    # Note, the measurement_system will return a list of selected values
    # in this case, we use the first one
    measurement_system = config_value('MyApp','MEASUREMENT_SYSTEM')
    return render_to_response('myapp/index.html',
                            {'image_count': image_count,
                            'measurement_system': measurement_system[0]})

Using the value in your :file:`index.html` is straightforward:

<p>Test page</p>
<p>You want to show {{image_count}} pictures and use the {{measurement_system}} system.</p>

Security and Restricting Access to Livesettings

In order to give non-superusers access to the settings, make sure to use the django user permission admin screen to give the desired user the livesettings|setting|Can change settting.


Superusers will have access to this setting without enabling any specific permissions

Permissions for insert, delete or permission for longsetting are ignored and only the above-mentioned permission is used. The same permission is needed to read values.

All views in livesettings support CSRF regardless of enabled or disabled CsrfViewMiddleware, because of the security significance of livesettings comparable to Django Admin.

If you want store sensitive information to livesettings on production site, e.g. a login password for a payment gateway to verify payments, it can be recommended to remove permission to livesettings at least from users which are beeing logged everyday including yourself, or the most secure is to export them and disable livesettings as described below. Exporting settings itself is allowed only to the superuser.

For password values it is recommended to define them by PasswordValue(... render_value=False) to be actual password not re-echoed to browser. Thought passwords are hidden by asterisks to human reader in the web browser, should be considered accessibility by attacker's javascripts.

Exporting Settings

Settings can be exported by the . After exporting the file, the entire output can be manually copied and pasted to :file:`` in order to deploy configuration to more sites or to entirely prevent further changes and reading by web browser. If you restrict DB access to the settings, all of the livesettings_* tables will be unused.

Here is a simple example of what the extract will look like:

{   1: {   'DB': False,
           'SETTINGS': {   u'MyApp': {   u'DECIMAL_TEST': u'34.0923443',
                                         u'MEASUREMENT_SYSTEM': u'["metric"]',
                                         u'PERCENT_TEST': u'0.251'}}}}

In order to restrict or enable DB access, use the following line in your settings:

'DB': True,    # or False

If you have multiple sites, they can be manually combined in the file as well, where "1:" is to be repeatedly replaced by site id.

Exporting settings requires to be a superuser in Django.


If you use logging with the level DEBUG in your application, prevent increasing of logging level of keyedcache by configuring it in

import logging

Next Steps

The rest of the various livesettings types can be used in a similar manner. You can review the satchmo code for more advanced examples.