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[1] 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 -------- [1] http://mezzanine.jupo.org/docs/configuration.html -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/3134004.Mo228LlGME%40devstation. For more options, visit https://groups.google.com/d/optout.
