#29776: Pulling part of django.conf.settings from the database
-----------------------------------+--------------------------------------
Reporter: Sven R. Kunze | Owner: nobody
Type: New feature | Status: closed
Component: Core (Other) | Version: master
Severity: Normal | Resolution: wontfix
Keywords: settings database | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+--------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => wontfix
Comment:
This isn’t something that would be added to core. There are various third-
party apps that do things in this area. See
[https://djangopackages.org/grids/g/live-setting/ Django Packages Live
Settings grid] for examples.
Additionally, for Email, your example, you could (e.g.)
[https://docs.djangoproject.com/en/2.1/topics/email/#defining-a-custom-
email-backend subclass the SMTP backend] to take it’s configuration from
the DB instead of the settings file.
I hope one of those routes help.
--
Ticket URL: <https://code.djangoproject.com/ticket/29776#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" 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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.797e022f82c8f9c999f7a70635fc33ab%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
