Re: [Django] #29776: Pulling part of django.conf.settings from the database

[Django]

#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:  needsinfo
 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 Sven R. Kunze):

 * status:  new => closed
 * resolution:   => needsinfo


-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.11ecce8e9c094298742bbbdcd6795745%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29776: Pulling part of django.conf.settings from the database

[Django]

#29776: Pulling part of django.conf.settings from the database
---+--
 Reporter:  Sven R. Kunze  |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Core (Other)   |  Version:  master
 Severity:  Normal |   Resolution:
 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
---+--

Comment (by Carlton Gibson):

 Searching mailing list for “dynamic settings” returns
 [https://groups.google.com/forum/#!searchin/django-
 developers/dynamic$20settings%7Csort:date a long list of historical
 discussions] of this sort of suggestion. (Including dynamic app plugins
 and everything else.)

 At this point I think it’s fair to say it’s been considered, and rejected
 as not feasible or worth the complications.

 To push it forward I think it would require a proof-of-concept in the form
 of a working thrid-party application. That those that have been attempted
 in the past are abandoned—if that’s true across the board—should tell us
 something. If you’re able to pick one up and make it work then a post to
 django-developers discussing whether it could be brought into core would
 be reasonable.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.e503844089d2a1cb49917d583a540ebb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29776: Pulling part of django.conf.settings from the database

[Django]

#29776: Pulling part of django.conf.settings from the database
---+--
 Reporter:  Sven R. Kunze  |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Core (Other)   |  Version:  master
 Severity:  Normal |   Resolution:
 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 Sven R. Kunze):

 * status:  closed => new
 * resolution:  wontfix =>


Comment:

 See ​Django Packages Live Settings grid for examples.

 I checked them out and any active one of these break compatibility :-(

 {{{
 from django.conf import settings  # won't work anymore
 }}}


 for Email, your example

 I don't see why Email should be special.


 This isn’t something that would be added to core.

 Which is unfortunate given the plethora of 3rd-party apps, including many
 old betas. If you change your mind, I can contribute pull requests.

 To me seems like a rather tiny but very core functionality (also enabling
 dynamic plugin apps etc).

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.6a2959d5a0cd54dbf6f8ee44e3556c48%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29776: Pulling part of django.conf.settings from the database

[Django]

#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: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
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.

[Django] #29776: Pulling part of django.conf.settings from the database

[Django]

#29776: Pulling part of django.conf.settings from the database
-+-
   Reporter:  Sven R.|  Owner:  nobody
  Kunze  |
   Type:  New| Status:  new
  feature|
  Component:  Core   |Version:  master
  (Other)|
   Severity:  Normal |   Keywords:  settings database
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 It would be great to have a way to specify settings variables (for
 instance EMAIL_HOST or EMAIL_PORT) e.g. in the admin interface (key-value
 store or json table).

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/050.c3d722189ecea34a03f9166be3147d22%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.