#14628: Document which settings can be changed at runtime
-----------------------------------------+----------------------------------
               Reporter:  NicoEchaniz    |         Owner:  nobody              
                 Status:  new            |     Milestone:                      
              Component:  Documentation  |       Version:  1.2                 
             Resolution:                 |      Keywords:  settings django.conf
           Triage Stage:  Accepted       |     Has patch:  0                   
    Needs documentation:  0              |   Needs tests:  0                   
Patch needs improvement:  0              |  
-----------------------------------------+----------------------------------

Comment (by NicoEchaniz):

 I do not agree with your assessment on this matter. Documenting this
 information would be very useful for anyone working on multi-tenancy for
 django projects. There are in fact certain scenarios where multi-tenancy
 is a valid - if not the only - deployment option.

 For reference, I'll add a link to the
 [http://www.revsys.com/officehours/2010/nov/05/#question5 full log of the
 chat session] that inspired the creation of this ticket.

 Documentation should state very clearly that runtime-modification of
 settings is something you should avoid unless you fully understand the
 consecuences.
 If there were consensus on the proper way to handle the threading issue, I
 think it should be documented too, but an enfatic warning would suffice
 for the time being to discourage people from fiddling with this lightly.

 I'd also like to add that this is just a documentation proposal on current
 existing features and as such I don't see how this could be of any harm
 unless it's done carelessly, which I find hard to expect knowing the
 general quality of django documentation.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/14628#comment:5>
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Reply via email to