============================= django-dynamic-preferences

.. image:: https://badge.fury.io/py/django-dynamic-preferences.png :target: https://badge.fury.io/py/django-dynamic-preferences

.. image:: https://readthedocs.org/projects/django-dynamic-preferences/badge/?version=latest :target: http://django-dynamic-preferences.readthedocs.org/en/latest/

.. image:: https://github.com/agateblue/django-dynamic-preferences/actions/workflows/tests.yml/badge.svg :target: https://github.com/agateblue/django-dynamic-preferences/actions/workflows/tests.yml

.. image:: https://opencollective.com/django-dynamic-preferences/backers/badge.svg :alt: Backers on Open Collective :target: #backers

.. image:: https://opencollective.com/django-dynamic-preferences/sponsors/badge.svg :alt: Sponsors on Open Collective :target: #sponsors

Dynamic-preferences is a Django app, BSD-licensed, designed to help you manage your project settings. While most of the time, a settings.py file is sufficient, there are some situations where you need something more flexible such as:

per-user settings (or, generally speaking, per instance settings)
settings change without server restart

For per-instance settings, you could actually store them in some kind of profile model. However, it means that every time you want to add a new setting, you need to add a new column to the profile DB table. Not very efficient.

Dynamic-preferences allow you to register settings (a.k.a. preferences) in a declarative way. Preferences values are serialized before storage in database, and automatically deserialized when you need them.

With dynamic-preferences, you can update settings on the fly, through django's admin or custom forms, without restarting your application.

The project is tested and work under Python 3.7, 3.8, 3.9, 3.10 and 3.11 and with django 3.2 and 4.2.