Is there a way to importing multiple .CFConfig.jso...
# lucee
d
Is there a way to importing multiple .CFConfig.json files at once to configure Lucee 6.2+? I'm working on updating our provisioning from Lucee 5 to 6. We are currently using a tool that we forked from something else which allows us to pass in JSON files to configure Lucee using a designated endpoint. We split our configs into multiple files, because we have like a "base" config and then configs that are specific to different environments. I'd like to migrate this over to .CFConfig.json. I know I can copy a .CFConfig.json to the deploy folder to have it picked up, but I'd hate having to copy each one over, wait for it to be applied, copy the next, etc. Is there a way we can either drop a bunch of files into a .CFConfig folder or possible having it pick up any file starting with .CFConfig?
b
Just go clarify, are you using CommandBox had having the CLI CFConfig tool import them, or are you specifying them directly to Lucee?
d
Not using CommandBox
👍 1
To answer my own question, in looking through the source code it appears at most you can import two files: .CFConfig.json config.json (well, technically if you're on a case sensitive OS it would appear you could use case variations of those file names to increase the total number of files, but that would be confusing to manage!)
z
Three is possible, you drop the base one in context and then the other two options. But why not just us
jq
and merge them before dropping them in deploy?
d
My plan was to merge them, but before doing work that might not be necessary, I wanted to see if I could just drop a bunch of *.json files in the folder and have them added. I might be totally unique, but it would seem like it would be nice to have a deploy/config folder where you could just dump a bunch of JSON files and have them merged. Have them processed in alphabetically order, so you could name your templates like 00-XX, 01-YY, etc to have them deployed in a specific order.