CFConfig must determine the server(s) on which to operate, which will either be a web context or a server context. CFConfig will determine the server as follows:
- By default, when the
to
orfrom
parameters are not present, CFConfig will use the current working directory, assuming it is the web root for an Embedded Commandbox Server (see below) - You provide a file path to the server home by using the
to
and/orfrom
parameters - You provide the name of a previously-started CommandBox server, using
to
and/orfrom
parameters (see Commandbox Managing Servers)
The folder containing the lucee-web.xml.cfm
file. An example would be:
<webroot>C:/myapp/WEB-INF/lucee/
cfconfig export from=C:/myapp/WEB-INF/lucee/ to=myconfig.json
Path to the lucee-server
folder containing the /context/lucee-server.xml
file. An example would be:
C:/lucee/tomcat/lucee-server/
cfconfig export from=C:/lucee/tomcat/lucee-server/ to=myconfig.json
The cfusion
folder that contains the lib/neo-runtime.xml
file. An example would be:
C:/ColdFusion11/cfusion/
Just provide the path to the JSON file. This is auto-detected if the path ends in .JSON
. An example would be:
C:/path/to/myConfig.json
Every command with a 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.
Format is specified as engine@version
where:
engine
is the name of the CF engineversion
is a semantic version number representing the engine version
Possible engine values are:
- luceeWeb - Lucee web context
- luceeServer - Lucee server context (Default for Lucee servers)
- adobe - Adobe server
- railoWeb - Railo web Context
- railoServer - Railo server context
Here are some examples of server formats:
- adobe@10
- [email protected]
- luceeServer@5
- [email protected]
If you run CFConfig from the web root of a Commandbox embedded server, you do not need to specicy the from
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.
cfconfig show fromFormat=luceeWeb
This example assumes you are running CFConfig from the web root of an embedded server:
cfconfig import from=config_admin.json toFormat=luceeWeb