I have just added CFConfig support for Lucee 6 and its new JSON format. I would love some people giving it a test and seeing if all your config imports correctly. Lucee JSON has a lot of differences to the CFConfig JSON format so I'm not too certain I'm mapping all the values properly. Please report back anything you find. Install the latest version of CFConfig to test.

Last time I tried it in Docker (some version of Lucee 5, I think? sometime near the first introduction of cfconfig into the official Live docker container) I was thwarted by a combination of no docs and failed trial and error due to no docs. Could someone give a few bullets (or point me to a how-to) on applying a small, verbatim, known-good configuration in a docker container that I could then build on?

I'm confused-- the CFConfig support I just added would be for use in the Ortus CommandBox container, or some other custom container in which you were manually using CFConfig. It wouldn't apply to any of Lucee's images.

Okay, ignore, then. I could swear cfconfig support was quietly added (but only tangentially documented). The conversation must have happened on Slack because I can't find it and I could be misremembering it.

Something called "CFConfig support" was added to Lucee 6, but as I found today, Lucee's file they now call

.cfconfig.json

is only similar to the actual CFCOnfig JSON spec. It's got tons of differences

That's gotta be what I tried (the .

cfconfig.json

), and I must have tried it (and failed) with Lucee 6. Once of these days I'll probably bite the bullet and go with the CommandBox image. I don't love templating

lucee-web.xml

and

scheduler.xml

.