.cfconfig.json
in the webroot, which will cause them to automatically get loaded in on every server start. This is the easiest way to share configuration with your coworkers. One issue with this may be that you don't want the json file in your web root in case it accidentally gets moved to a production server and it directly accessible. Web servers such as Apache will not serve files starting with .
by default, but other web servers will happily share those "hidden" files. You can work around this by placing the JSON file outside the web root and using the cfconfigFile
property in your server.json
to point to it. You can use relative paths like ../build/mySettings.json
.server.json
keys specifying JSON file locations).${mySetting}
and would look like so in your JSON file:adminPassword
setting with the value of an environment variable called LOCAL_DEV_CF_PASS
.${name:default}
.LOCAL_DEV_TIMEOUT
.cfconfigFile
in server.json
, set the CFConfigPauseTasks
setting to true with server set CFConfigPauseTasks=true
.--pauseTasks
flag i.e. cfconfig import myConfig.json --pauseTasks
.