mirror of
https://github.com/jazzband/django-constance.git
synced 2026-03-16 22:40:24 +00:00
Docs tweaks.
This commit is contained in:
parent
2c03498d91
commit
7bd1513a4f
2 changed files with 14 additions and 1 deletions
|
|
@ -87,6 +87,18 @@ make sure the data model is correctly created::
|
|||
'constance.backends.database',
|
||||
)
|
||||
|
||||
Please make sure to apply the database migrations::
|
||||
|
||||
python manage.py migrate database
|
||||
|
||||
.. info:: If you're upgrading Constance to 1.0 and use Django 1.7 or higher
|
||||
please make sure to let the migration system know that you've
|
||||
already created the tables for the database backend.
|
||||
|
||||
You can do that using the ``--fake`` option of the migrate command::
|
||||
|
||||
python manage.py migrate database --fake
|
||||
|
||||
Just like the Redis backend you can set an optional prefix that is used during
|
||||
database interactions (it defaults to an empty string, ``''``). To use
|
||||
something else do this::
|
||||
|
|
|
|||
|
|
@ -50,7 +50,8 @@ Here, ``42`` is the default value for the key ``THE_ANSWER`` if it is
|
|||
not found in the backend. The other member of the tuple is a help text the
|
||||
admin will show.
|
||||
|
||||
See the :ref:`Backends <backends>` section how to setup the backend.
|
||||
See the :ref:`Backends <backends>` section how to setup the backend and
|
||||
finish the configuration.
|
||||
|
||||
Usage
|
||||
-----
|
||||
|
|
|
|||
Loading…
Reference in a new issue