is there a key reference for CFConfig? i'd like to know if there's a more efficient way of figuring out the mappings between cfconfig.json and the lucee admin. currently, my process is indirect: make changes to the admin, export to json, diff, repeat.

thanks, @cfsimplicity

@jamiejackson CFConfig does not provide any defaults. If the key isn’t provided in the

.cfconfig.json

file, the engine defaults are used - and nothing is changed within the engine exisiting settings

side question: that's not true of lucee 6, tho, correct? i had a conversation with @bdw429s recently and i thought lucee 6 had to be spoonfed its own defaults when importing to the new lucee json format.

That is half true. When importing a file, we won't import anything you don't ask for. That said, when you import into a directory/server that doesn't exist yet (which happens on a first-start scenario), then there is an actual default config template we use

got it. and defaults for 5 come from this? https://github.com/Ortus-Solutions/cfconfig/blob/master/resources/lucee5/lucee-web-base.xml

Here are the defaults for Lucee 5 https://github.com/Ortus-Solutions/cfconfig/tree/master/resources/lucee5

i'm converting from xml templates to cfconfig in 5 as a preliminary step to going to lucee 6. once in 6, i plan to go to single context mode anyway.