http://coldfusion.com logo
Join Slack
Powered by
A little late to the game, but I've added ACF 2025...
# cfml-general
a
A little late to the game, but I've added ACF 2025 to TryCF.com Try it here
🎉 5
👍 3
👍🏼 1
b
@abram 2025 update 1 came out this week. Did you install 2025.0.0 on purpose?
f
Thanks Abram!
🍻 1
a
@bdw429s I'm using the env var 
BOX_SERVER_APP_CFENGINE=adobe@2025
to specify the engine.
b
@abram Can you get me the console output of the start command?
Thus is what I'm seeing
Copy code
| √ | Installing package [forgebox:adobe@2025]
   |   |-------------------------------------------------------
   |   | Verifying package 'adobe' in forgebox, please wait...
   |   | Installing version [2025.0.01+331420].
   |   | Verified entry in forgebox: 'adobe'
   |   | Deferring to [https] endpoint for forgebox entry [adobe]...
   |   | Downloading [<HTTPS://downloads.ortussolutions.com/adobe/coldfusion/2025.0.01/cf-engine-2025.0.01.zip>]
   |   | Decompressing...
   |   | Storing download in artifact cache...
   |   | Done.
And the CF admin confirms, 
2025.0.01.331420
is installed
a
oh, interesting. So I'm using the base docker image 
ortussolutions/commandbox:adobe2018-alpine
and the logs indicate:
Copy code
Contacting ForgeBox to determine the latest & greatest version of [ad
   | obe 2025]...  Use an exact 'cfengine' version to skip this check
   | OK, [adobe 2025.0.01+331420] it is!
   | You've asked for the engine [adobe@2025.0.01+331420] to be started,
   | but this server home already has [adobe@2025.0.0+331385] deployed to
   | it
   | In order to get the new version, you need to run 'server forget' on t
   | his server and start it again
b
yep, that'll do it'
now, I don't quite understand why the 2018 tag has 2025 🤔
a
sorry, wrong copy/paste
b
but you can't use a pre-warmed container and also get the latest
a
ortussolutions/commandbox:adobe2025-alpine
👍 1
b
you'll get what the container has already warmed up and nothing else
your env var is basically useless
if you want the env var to control the CF version, then use our vanilla container with no engine warmed in it yet
This is true of all CF engines in a prewarmed container
👍 1
a
Yeah, I use the jdk<v>-alpine image elsewhere. I'll swap that out.
b
prolly a good idea. @jclausen normally re-builds our docker prewarmed containers when engines come out, but not always right away.
👍 1
j
Yeah. I can get those built today.
👍 1
a
ok, redeployed with the jdk image: 
2025,0,01,331420
👍 1
j
The updated docker images are published as well now.
🙏 1
2 Views
Open in Slack
PreviousNext
Powered by