I’d like to start a discussion to break down the functionality of config.yml, what it can, and what it can’t be configured to do. My understanding so far is that it ports the settings to the lms.env.json config file and reloads these on
tutor config save and initiate them on
tutor local quickstart.
But does it also redirect settings to cms.env.json? And what about cms.auth.json and lms.auth.json?
Are all the FEATURES: parameters supported, and do I need the heading FEATURES in config.yml, or will it know?
I’m trying to build an understanding so that I can plan a way to preserve my settings regarding:
ENABLE_LTI_PROVIDER, ENABLE_THIRD_PARTY_AUTH, THIRD_PARTY_AUTH_BACKENDS,
and in the lms.auth.json:
Hoping for more insight!