cfml

<@U06V253M4> Is there a way to tell what embedded version of lucee box is running? If I execute `box task run whatever.cfc` will it honour `ENV BOX_SERVER_APP_CFENGINE=lucee-light@5.3.9.133` and use that engine or is there a way to set the internal engine?

That was one of the slides in my hidden gems/tips and tricks session at ITB last week :slightly_smiling_face:

You asked about running a task but your example is an environment variable that servers use so I'm unclear if you're starting a server from the task or what...

But if the env var is set, then yes it's going to get used!

Sorry for delay, team meetings... <@U06V253M4> So what's happening is in our dockerfile we are pre-compiling our cfm/cfc code into .lar files with a `box task run build.cfc compile` step, my build.cfc is using lucee admin's createArchiveFromMapping() and then those compiled files are put in place for the docker image to server.

I posted details of a problem in <#C06TA0A9W|lucee>, it seems like this migh be causing a problem with extension compatibility because `box task` is using a different lucee version (box info says lucee 5.3.9.160) than the actual docker lucee server which is lucee-light 5.3.9.133...

so I'm guessing its not possible to change or specify box's internal lucee version, it's baked in? So when box is updated (or the docker image ortussolutions/commandbox which has it) and the version mismatches is where we run into this issue

<@UHVA0EUR1> You can downgrade the lucee.jar in the CLI but that's at your own risk.

Is the issue really the Lucee version or is it the version of the _extensions_ that are installed?

Because you can also influence the extension versions the CLI use too.

Also, have you seen Pete Freitag's CFML compiler project?  It starts a server and lets you choose a specific version

We download the lex extensions in the docker build directly into the `${BOX_SERVER_APP_SERVERHOMEDIRECTORY}/WEB-INF/lucee-server/deploy/` folder, in this case s3 v0.9.4.154 and everything was working fine, it was only when we did a deploy last night that it must have picked up a new version of the base ortus docker image with a new box version, and new lucee version 5.3.9.160 that does the compile that wanted s3 v0.9.4.155-SNAPSHOT that we ran into this issue

I'll have to take another look at cfml-compiler, I believe its doing the same thing under the hood, I guess I didn't realize that `box task` could be a compatibility issue

Oh no his compiler is compiling the individual files in place, it doesn't combine them into a lar archive (though thats not really the important part)

I'd recommend just doing it within your actual  live lucee install via

`admin action="compileMapping"`
                    `type="server"`
                    `password=request.SERVERADMINPASSWORD`
                    `virtual="/"`
                    `stoponerror="false";`