Here is the slide deck for my talk CFConfig -- A new way to manage your ColdFusion engine config that I presented at Adobe ColdFusion Summit 2017.
In this talk, we will learn about a new library for the answer you’ve been looking for if ever you wanted to script out the complete setup of a server without manually copying XML files around. CFConfig is a command line library that is built on top of CommandBox so it can be run anywhere by hand or as part of an automated script. The CLI can be used for Vagrant or Docker provisioners or custom setup scripts. The pure service layer’s fluent API can be integrated into any CFML project for mashups outside of the CLI. We’ll dig into this new library, what is is, how to use it, and most importantly how to contribute back to the project if you want better support for a particular engine.
In a nutshell, this project can be used to read and write ColdFusion configuration from any version of any CF engine in a generic format that let's you separate the setup of your servers from the actual installation. Here's some examples:
- Export config from a server as a backup
- Import config to a server to speed/automate setup
- Copy config from one server to another. Servers could even be different CF engines
- Merge config from multiple servers together.
- Facilitate the external management of any server’s settings without needing to log into the admin UI.
We'll cover the generic JSON format that's used and talk about how you can distribute your coded with a full generic set of configuration including CF mappings, datasources, custom tags, or request timeouts without needing to worry about what version of CF the end user is going to have. This tool is a must for anyone using Vagrant, Docker, local develop