Django Stored Settings
It often happens that we need to be able dynamically to create/edit some settings and site variables, for example site title, logo and counter code.
stored-settings module is tailored specifically for these purposes allowing dynamically to create and further on to edit via django-admin records of the following types:
Char
Text
HTML text
Boolean
Image
Requirements
Django stored-settings requires Django 1.3 or later and Pillow. Also has TinyMCE integration.
Getting It
You can get Django stored-settings by using pip or easy_install:
$ pip install django-stored-settings or $ easy_install django-stored-settings
If you want to install it from source, grab the git repository from GitHub and run setup.py:
$ git clone git://github.com/zvadim/django-stored-settings.git $ cd stored_settings $ python setup.py install
Installing It
To enable stored-settings in your project you need to add it to INSTALLED_APPS in your projects settings.py file:
INSTALLED_APPS = (
...
'stored_settings',
)
And also add new content processor
TEMPLATES = [{
...
OPTIONS': {
'stored_settings.context_processors.stored_settings',
...
},
}]
Last step is db migration
$ python manage.py migrate
Using It
in template {{ stored_settings.my_key }}
TinyMCE
For HTML fields TinyMCE can be applied. To enable TinyMCE support in stored-settings you need to add to settings.py the following:
STORED_SETTINGS_TINYMCE_ENABLE = True
Metadata
Release files for django-stored-settings 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| django-stored-settings-0.2.1.tar.gz | 5.2 kB | Without provenance | Details for django-stored-settings-0.2.1.tar.gz |
Release files / django-stored-settings-0.2.1.tar.gz
| Download URL | django-stored-settings-0.2.1.tar.gz |
|---|---|
| Size | 5.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
523dc3bb055f0d1044ad7e90df45ba0c03c45153dfcde50072d6835599c46b3d
|
|
BLAKE2b-256 checksum How to use checksums |
fa392b7d50f3e44d0727255e57ef9cdc8980c0e436d72bbb94fc2631a84db459
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-stored-settings 0.2.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.