Document which settings can be changed at runtime
|Reported by:||NicoEchaniz||Owned by:||nobody|
|Cc:||nico@…, andybak, danny.adair@…, tom@…||Triage Stage:||Accepted|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
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.
Change History (11)
comment:1 Changed 3 years ago by jacob
- Needs documentation unset
- Needs tests unset
- Patch needs improvement unset
- Summary changed from missing documentation about which settings can be safely changed at runtime to Document which settings can be changed at runtime
comment:8 Changed 3 years ago by andybak
- Cc andybak added
- Severity set to Normal
- Type set to Uncategorized
comment:10 Changed 3 years ago by Danny W. Adair <danny.adair@…>
- Cc danny.adair@… added
- Easy pickings unset
- UI/UX unset