CFConfigServerit will be used as an absolute path to the JSON file or a relative path in relation to the web root.. An example of setting this in Windows would be:
cfconfigseverat the same time since they do the same thing. They are both provided for consistency. If you use both, they will all be imported!
server.jsonproperty, but given the options above, it's not necessary to use these unless you want to or specifically want to override the settings in the
CFConfigproperty in your
server.jsonfile, it will be used to help control how your JSON configs are imported. All JSON file paths can be absolute or relative paths from the folder the
cfconfig.file. For a Lucee server in which you want to import settings into the server AND web context, you can use
cfconfigfileenvironment variable set as well as a
cfconfig.filekey in your
server.json. In this case, BOTH JSON files will be imported. When there are two more more JSON files being imported into the same web or server context, the first file will be an overwrite as usual and all subsequent files will be imported in "append" mode so they add to the settings in the previous file.
.cfconfig.jsonFile in Webroot
server.jsonproperties) are found to specify a JSON file to import, CFConfig will look for the following files in the web root by convention.
.cfconfig.json- Use this for Adobe or for Lucee's server context
.cfconfig-web.jsonUse this for the Lucee web context
.cfconfig-server.jsonUse this for the Lucee server context (same as
.cfconfig-server.json, it will still be used but just imported into Adobe's single context.
cfconfig_will be used. The naming format is
xxxis the name of a valid config item such as
adminPasswordsetting is present in an auto-imported JSON file or a
cfconfig_adminPasswordenvironment variable is set on a Lucee server, the server start interceptor will set that password into the web context as well as the default server context. This is to prevent a production server getting deployed with no password on the web context.
cfconfig setcommand, it's up to you to also set things like passwords into the server and web contexts.
production, CFConfig will not allow your sever to start with an empty password or with the Adobe default password of
commandbox. If any of those scenarios are detection in a
productionprofile, CFConfig will set a random password and output it in the verbose console logs for you to refer to later.