#14628: missing documentation about which settings can be safely changed at
runtime
----------------------------------+-----------------------------------------
Reporter: NicoEchaniz | Owner: nobody
Status: new | Milestone:
Component: Documentation | Version: 1.2
Keywords: settings django.conf | Stage: Unreviewed
Has_patch: 0 |
----------------------------------+-----------------------------------------
The current documentation about settings states that they shouldn't be
changed at runtime. But there are deployment scenarios - eg. multi-tenancy
implementation - where this is necessary.
A bit of IRC chat with jackob k.m. regarding this issue is quoted below:
{{{
[15:22:58] <jacobkm> nicoechaniz: I keep meaning to actually run through
all of them and put together some documentation on which can and can't be
modified at run time.
[15:23:09] <nicoechaniz> jacobkm: yeah, we have been banging our heads
with that precise issue : )
[15:23:27] <nicoechaniz> jacobkm: that would really be great
[15:23:29] <jacobkm> nicoechaniz: yup, me too. It's tricky, and we've done
a bad job internally being clear about which settings are which.
}}}
The problem with settings is that some of them are used only on project
initialization and others are actually used throughout the process
lifetime. The second kind could be changed at runtime, but there's no way
to know which setting falls into which group without going through a lot
of trial and error.
--
Ticket URL: <http://code.djangoproject.com/ticket/14628>
Django <http://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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
