Anybody know how to properly expose a commandbox server running inside a docker container? Hoping to hit it from a web browser outside the container but I'm getting ERR_EMPTY_RESPONSE, whereas inside the container I can curl it just fine. More specifically, I am running a Lucee container for my main app and using commandbox at this time for testbox. I have the port mapped correctly (42518:42518). My (8080:80) port mapping for the main application works fine. I tried setting host of the commandbox server to 0.0.0.0, which of course DOES expose it outside the container (via localhost:42518) but all I see is "Forbidden" on the page.

@Jason Ryan What image are you using?

ortussolutions/commandbox

?

Using the standard lucee docker image, not commandbox (we'd like to move to that at some point)

Hmm, is that an

<h1>

?

Here is hte output log of how I'm starting it

Hmm, not undertow

Inside the

lucee:5.3.10.120-light-nginx

image I have this step to install commandbox

That's super confusing, lol

Yeah, it doesn't seem ideal. Commandbox was added after the fact for migrations, cfconfig, and now testbox. We should totally backup and only use commandbox right?

If you just want to start a server, you can use

ortussolutions/commandbox

and map your code into

/app

but a lot of this depends on what your expectations are and how your app is set up.

Ok yeah that's not a bad idea, I can just spin up another container for the tests

The CommandBox docker image expects you to use

server.json

and a specific set of env vars to configure it (CFConfig too)

Yeah, every time I look at the docs it amazes me how much more you can do with the commandbox image

But I don't know what your constraints are-- if your coworkers already decided they wanted to use the Lucee image instead for some reason then a convo of switching base images may be out of the question

Yeah that's not the case, its almost tech debt at this point being on the Lucee image, dev time is the constraint

Now as far as running tests-- that's another can of worms. That can mean different things. Are you intending to use the CLI

testbox run

command, or do you just want to hit them in the browser, etc, etc?

Yes I have success with using the

testbox run

command in the CLI, we use that in our CI/CD for example. The reason I wanted to hit it in the browser is for better debugging capabilities, as in seeing my output (I posted about this earlier and someone recommended to hit it in the browser)

Which boils down to how you are trying to consume them. A browser, a

curl

command,

testbox run

, etc

I guess I was looking to do both? I like the CLI for just seeing overall response of the test and for the watch capbiliy. But if I'm digging into an issue with on of the tests I want to output things and see them so the browser seems ideal for that

If you're just playing with the tests, I would just run the locally. And I don't use docker for local dev. Just a good old CommandBox server

Yeah I can access the actual app no problem

so add

/tests/runner.cfm

to the end 🙂

The testbox runner sits just outside the webroot that my actual app serves, so yeah I'd have to modify its location to hit it in the url like that

Well, if this is local, I'd ditch docker entirely,

Yup its local

but generally speaking, there's no particular reason to run the testbox run inside the container if the container is only there to start the site up

I had it setup that way for better portability amongst the devs, one less dependency to install themselves haha

CommandBox is designed to be a general purpose CF developer tool that you install directly on your PC and if you point the

testbox run

command at a URL that happens to be hosted on a docker container, the CLI doesn't even care

That's great to know. You've given me multiple ways to go about this 🙂

With CommandBox alone, which just requires a

box.exe

to be dropped on the desktop, a new develpepr workflow is literally just

git clone ...
box install
box start

You gotta add it to your path in windows tho right?

You've already got the server auto-installed by a binary that works the same on Mac, Linux, and Windows

Haha fair enough

IN fact, you can run the git command from INSIDE the interactive shell 🙂

Did not know you can run git in there. That's awesome. Commandbox is legit

you can run any native binary with

!

in front

Yeah I can see that. We do use docker compose to run 2 services, lucee and postgres

Heck, CommandBox servers even let your force case sensitivity to be on or off so Windows and Linux devs have the same experience

I'm definitely inspired to use commandbox more 😄

Here's this if you have some reading time https://commandbox.ortusbooks.com/