When I use docker commandbox, how can I specify th...
# docker-commandbox
p
When I use docker commandbox, how can I specify that when I start the server robust debugging is enabled?
b
@paul Are you referring to a CommandBox settings, or an Adobe CF setting, or a Lucee Server setting?
p
Sorry I'm referring to both AFC and Lucee so I can see all the exceptions.
b
You can enable that with CFConfig
Either by supplying a JSON file that contains that setting or putting an env var in the container
I don't think Lucee has the same setting Adobe has in this case
I assume you want
robustExceptionEnabled
which only affects Adobe
so
Copy code
{
  "robustExceptionEnabled": true
}
or
Copy code
ENV cfconfig_robustExceptionEnabled=true
p
Copy code
version: '3'
services:
  cfml:
    image: ortussolutions/commandbox
    #depends_on:
    #  - postgres
    environment:
    - BOX_SERVER_APP_CFENGINE=adobe
    - cfconfig_robustExceptionEnabled=true
    volumes:
      - ./app:/app
    ports: 
      - "8080:8080"
b
What version of Adobe?
if it's 2021, you must also install the debugger module in order for the setting to actually do anything
But I'd start by logging into the admin to see if the setting was stored
Also, review the console output and see if CFConfig set the setting
p
[robustExceptionEnabled] set.
I forgot about the modues in 2021 thanks. Thats probably it
b
There is a env var for that
I THINK it's
CFPM_INSTALL
but you can confirm in the docs
p
Thanks, now I need to find that exat moduel, no list on Adobes website for that
Do you know where cfpm is ont he command box image so I can exec into it to look at that list?
Oh it lists them when the conatiner starts
@bdw429s is cfide blocked by default?
Got it: - BOX_SERVER_WEB_BLOCKCFADMIN=false
- CFPM_INSTALL=administrator,debugger
Actually it didnt work as the dubuuger didnt install, but if I manually install that model in cfadmin it works
I don;t think this is the env it listens to
CFPM_INSTALL
Docs indicate that it is:
Copy code
CFPM_INSTALL and CFPM_UNINSTALL - Supported for Adobe Coldfusion 2021 engines. When provided as a delimited list of Coldfusion Package Manager packages, these will be installed ( or uninstalled, respectively ), prior to the server start. A warmed-up server is required to use these variables.
But I guess I have to build a conatiner ontop on the base so it's warm.
b
@jclausen A while back, you and I discussed moving the CFPM installation until after the dry run and before the start script in the Docker images. Do you recall if that change was ever made?
j
@bdw429s Yes. If the dry run flag is up, then CFPM runs after that completes. https://github.com/Ortus-Solutions/docker-commandbox/blob/development/build/util/start-server.sh
b
Hmm, then it sounds like Paul shouldn't need to create a base image then, right?
@paul Perhaps you can report the console output when the container starts
j
He should be able to use the 2021 image and then either finalize it or run it with the install on demand.
b
but even if he uses the vanilla image, that should still work in my understanding.
j
Yes, though it would be slower to build having to download the 2021 engine.
b
So long as the container start is doing this: • dry run that generates start script and unzips server home • CFPM install • actual server start
j
Bingo
b
it would be slower to build having to download the 2021 engine.
Yes, for sure!
p
I'll do all the reports and info for you both, just in the "normal" work day not the fun parts of the day.