to
or from
parameters are not present, CFConfig will use the current working directory, assuming it is the web root for an Embedded Commandbox Server (see below)to
and/or from
parametersto
and/or from
parameters (see Commandbox Managing Servers)lucee-web.xml.cfm
file. An example would be:lucee-server
folder containing the /context/lucee-server.xml
file. An example would be:cfusion
folder that contains the lib/neo-runtime.xml
file. An example would be:.JSON
. An example would be:to
and/or from
parameter also has a matching toFormat and/or
fromFormat` parameter. In most cases, you don't need to provide this. If you are pointing to an existing CommandBox server, or typical server installation, CFConfig will examine the files in the CF home to determine what engine and version it is. However, if you are writing files to an empty or non-existent directory, you'll need to tell CFConfig what format to write them in.[email protected]
where:engine
is the name of the CF engineversion
is a semantic version number representing the engine versionfrom
or to
parameters to reference it, and CFConfig will automatically default to the luceeServer
format, which operates on the server context. If you wish to interact with the web context (which has little distinction in a CommandBox server since there's only one web context per server) you will need to provide the explicit luceeWeb
format by using either the toFormat
or fromFormat
parameters.