Otherwise you need to define it in your docker setup via

BOX_SERVER_PROFILE

if it isnt Production

Thats how I see it on here: https://hub.docker.com/r/ortussolutions/commandbox/

Because that was actually fixed in the latest version: https://github.com/Ortus-Solutions/docker-commandbox/issues/71

I tested the ability set that environment variable.

All

BOX_

environment variables would pass through to CommandBox

But when I run it the logs show:

Looking for server JSON file by convention: /app//server.json
webroot defaulted to location of server's JSON file: /app/
start server in - /app/
server name - app
server config file - /app//server.json

Update: This does not appear to be an issue with the container itself, but something with CommandBox. When I start a server in debug mode and that environment variable set and pointing to a different file, it appears to use a default file name.

√ | Starting Server
   |------------------------------
   | start server in - /Users/jonclausen/tmp/server-json-test/
   | server name - server-json-test
   | server config file - /Users/jonclausen/tmp/server-json-test//server.json

When I stop the server or forget it, the environment variable appears to get picked up and I see this output:

√ | Overriding server.json values from env vars
   |----------------------------------------------------------
   | Overridding [SERVERCONFIGFILE] with box environment variable [BOX_SERVER_SERVERCONFIGFILE]
   |----------------------------------------------------------

I am going to submit a ticket for @bdw429s to look at on this. I know this environment variable was working previously, so this may be a regression introduced later on in the beta phase of 5.8

I have created COMMANDBOX-1575 to track this issue.

@jclausen As a temporary workaround I changed the name of my file to

server.json

and it does then get read by commandbox.

Looking for server JSON file by convention: /app//server.json
webroot pulled from server's JSON: /app/web/
start server in - /app/web/
server config file - /app//server.json

As you can see, and for the reasons I mentioned before, I'm setting the webroot to be one level below in

/app/web/

However, I'm getting the following error which prevents the server starting:

[INFO] 2023-03-17T16:05:02Z - Starting server using generated script: /usr/local/bin/startup.sh
mv: cannot stat '/app/server-start.sh': No such file or directory

I've seen elsewhere that this error can be caused by using a pre-warmed image where the server.json has been already baked in, but that's clearly not the case here. My dockerfile is pulling the non-tagged base image and as you can see my server.json is being correctly read.

@cfsimplicity Apologies. I got sidetracked for a bit, but the new image version is published and available, which should solve the error.