Thanks for your help guys, I’m getting back to this finally.
Big picture: This is an app that interacts with other sites. That main app is running fine locally on CommandBox. The problem is that the source tree contains code for two test sites intended as test targets; they aren’t part of the app itself.
The main app needs to be able to hit each of these test sites at different absolute URLs. Access from off the box isn’t necessary, so host file entries are fine. Non-standard ports are ok. (The main CommandBox instance, i.e., the main app, is already on one.)
If the source for the test sites wasn’t inside the main app tree, running separate CommandBox instances would be the way to go. As it is though, I don’t see a way to tell the main CommandBox instance that these two dirs inside the root CommandBox is serving should NOT be served by it, but instead should be handled by two other instances. In other words, I effectively need atwo separate servers running code that’s inside a different one.
I totally understand that this is very much an outside edge case, and I’m not suggesting that anything about CommandBox should be different. I’m just trying to figure out how to get this odd configuration running somehow, so I don’t have to abandon CommandBox as my dev environment for this app, and move to discrete Lucee instances running on Apache, which is what everyone else is doing.
Is it possible to run CommandBox instances behind Apache? Roughly how, and is that documented somewhere?
Big big picture, CommandBox has a bunch of advantages as a dev environment, so I’ve been using it myself, hoping to eventually bring it forward to everyone else as a good way to go. But along the way, this wrinkle appeared in how things are configured for this app, and I’m pretty much at a fork in the road, get it working or bail.
Thanks again for any ideas,
Dave