Question about commandbox embedded server development: I'm porting my dev environment over to a Mac from Win10. I want to use commandbox as my runtime environment, which I have more or less setup. Currently, I can access the site and the Lucee admin, and I'm questioning my next steps. I would like to be as portable as possible and avoid having to manually enter a bunch of stuff in the lucee admin, like caches, datasources, email, etc. I assume I'll use cfconfig, but I'm wondering if I should first manually enter all the lucee stuff in the lucee admin, and then use cfconfig to export that information into a file that can be reused. Or is there a better way to approach this?

@redtopia That's one way to do it, but why not just export your previous settings from the old server?

from my windows machine?

yeah

ok... and then how do I get those settings into my commandbox instance? Do I use cfconfig?

Yes

just the first time after I run the new instance?

Just having CFConfig installed will pick up the

.cfconfig.json

file by convention every time the server starts

oh okay

Run

coldbox create app

in an empty folder if you want to see how we usually set it up

so right now, I have server.json sitting out at the root of my app... you're saying create a .config.json file in the root as well, and then whenever commandbox runs, it will use that .cfconfig.json file?

ok... but a lot of those settings I might move to the web context. I currently have them in my server context because I am not currently using commandbox on windows

And if you want to be really lazy, you can even have CFConfig put in the env var replacements and create the

.env

file for you https://cfconfig.ortusbooks.com/using-the-cli/command-overview/export-settings#json-expansion-replacements

I assume I should be putting all my settings in the web context?

I don't see what windows has to do with whether you use the web or server context.

if I put them in the server context, is that still isolated from other commandbox embedded server instances?

I see no reason to ever use the web context for anything unless • you're using ModCFML and have more than one of them • you're storing scheduled tasks

okay... that's good to know. I wasn't sure about that... I thought that maybe the server context was global

But regardless, CFConfig supports web contexts all the same https://cfconfig.ortusbooks.com/using-the-cli/json-file-storage#separate-lucee-railo-server-web-context-config

Thanks Brad... this is helpful

@redtopia There's not enough information for me to answer this question. is the Windows server a CommandBox server?

yea, windows... I figured it out. I specified from=c:/lucee/tomcat/lucee-server and it seems to have worked

You keep saying "windows" as though it has some bearing on how Lucee is installed. But it doesn't 🤔

is there a way to modify tomcat settings? I've made a few changes to allow me to upload huge files, and I also had to make a change to enable websockets.

I'm assuming the old server was not a CommandBox server, and was just a traditional Tomcat-based Lucee instance where you used the installater.

yes, correct

Then you' use this portion of the docs https://cfconfig.ortusbooks.com/using-the-cli/usage#lucee-4-5-server-context

ok... makes sense. Is there a way to modify the settings of the server to enable large file uploads and websockets, and that sort of thing?

We use JBoss Undertow and their correlating setting appears to be https://undertow.io/javadoc/2.0.x/io/undertow/UndertowOptions.html#MAX_ENTITY_SIZE

Thanks Brad

Undertow also has a

MULTIPART_MAX_ENTITY_SIZE

setting which may or may not apply based on your form type

lol thanks Brad