On Monday 27 March 2017 05:41:28 Det S. Pillner wrote:
> I work on tools for my job based on Django 1.8.17. In different
> projects (with different databases) I use same routine to get some
> data (config data). My problem is: the way is every time the same:
> import model, get config data from database. The difference is: model
> name is in every database different.
Django has a settings framework.
Mezzanine has built on that to make settings stored in database *and* support multitenancy through the django.contrib.sites framework and supports per-app defaults for free.
Why would you need yet another way?
--
Melvyn Sopacua
No comments:
Post a Comment