-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Labels
code healthProactive technical investment via refactorings, removals, etc.Proactive technical investment via refactorings, removals, etc.documentationRelates to documentation improvementsRelates to documentation improvementsinitiativeHuge unit of work, consisting of multiple epicsHuge unit of work, consisting of multiple epics
Description
Intended final settings structure
Open questions
- When exactly do we "rebase" Tutor's settings onto (lms,cms)/envs/(common,development)? Most likely, we should do it all at once when those four files are ready, as Tutor's settings are all coupled together into a Jinja hierarchy.
- Should the settings object should have same type signature between LMS and CMS?
Some general Testing Notes (Update as we improve this)
- Use the Settings Diffing tooling to check this
- See the testing instructions in previous PRs here:
Sub-issues
Metadata
Metadata
Assignees
Labels
code healthProactive technical investment via refactorings, removals, etc.Proactive technical investment via refactorings, removals, etc.documentationRelates to documentation improvementsRelates to documentation improvementsinitiativeHuge unit of work, consisting of multiple epicsHuge unit of work, consisting of multiple epics