That sounds like a great workflow. Depending on your deployment process, things like adminPassword are built into our Docker images via environment variables so you don’t even have to have them in the JSON. For instance, with our CommandBox Docker container (that bakes in CFCOnfig) you can simply set an env var called “cfconfig_adminPassword” and it gets picked up. So tons of options, and no real right or wrong way so long as it works for you.
Dave. if you’re still paying attention to this thread, I’m upgrading to JLine3 in CommandBox 4.0 (the library that handles our terminal interaction) and it has some nice new handling options so I can intercept Ctrl-C and Ctrl-D separately. These are raised as signals from the native terminal and I can configured JLine3 to throw an exception that I can catch.
In CommandBox 4.0, Ctrl-C will exit any currently running command (at least, if it’s waiting for user input) but it will NOT exit the interactive shell. Ctrl-D (which is the key code to send an end of file signal) will exit the entire shell like Ctrl-D used to.
Cool. I hadn’t been watching this thread, just happened to see it looking for something else, but that’s great, I exited by accident just the other day
