Skip to main content
J
joeyg60012433
Inspiring
February 27, 2025
Answered

Coldfusion 2023 Silent Zip Install using built in webserver

  • February 27, 2025
  • 1 reply
  • 392 views

We're upgrading from Coldfusion 2016 to 2023 for development on our laptops. We are attempting to make 2023 a silent install zip package. I've used the instructions here and was able to get into CFAdmin: https://helpx.adobe.com/coldfusion/using/install-coldfusion-zip.html

 

The admin is running on port 8500. However, I can't manage to see any other files in http://localhost:8600/ besides the usual CFIDE, cf_scripts, restplay, and crossdomain.xml.

In 2016 from what I remember, we just put our application files in wwwroot and didn't have to do anything else.

 

So I'm not sure if the zip installer installs the built in webserver? Or maybe it doesn't enable it? My server.xml looks just like the 2016 version. I'm at a loss.

Correct answer joeyg60012433

Welp turns out our software guys installed it to more than one location and I was looking at the wrong folder. Thank you and ignore this 🙂

1 reply

Charlie Arehart
Community Expert
Charlie ArehartCommunity Expert
Community Expert
February 27, 2025

It does, and it's at 8500, serving also that CF admin that you find working.

/Charlie (troubleshooter, carehart. org)
Charlie Arehart
Community Expert
Charlie ArehartCommunity Expert
Community Expert
February 27, 2025

And you CAN put your code in the cfusion/wwwroot (under where you extracted that zip), just like you did in 2016. You'll see that has the CFIDE folder for the admin, as well. 

 

All that said, please know you don't HAVE TO use the zip approach. That's new since cf2021 and is merely an option. There's also a full installer (like before), and that supports silent install as well. 

 

And in either approach (zip or full), yet another option is that you could implement your own separate web server (apache or iis), then use the traditional cf web server config tool to connect that to cf. Then you could put your code in a web root of your own choosing, as set in that web server. You'd then only use the 8500 for the cf admin.

 

This makes a local cf deployment feel closer to what would be a typical server deployment. Different strokes for different folks. There's also the option of deploying cf using containers, war files, Commandbox z and more. (FWIW, I have a preso on the many ways to run cf, at carehart.org/presentations.)

/Charlie (troubleshooter, carehart. org)
J
joeyg60012433Author
Inspiring
February 27, 2025

We use wwwroot in development because it's easier because our PCs are so locked down.

ZIP was the first thing I found and working to make it a package in our SCCM has been a pain enough. But I think we're good.

We already have 2023 on our servers and we use IIS. It's just been way past time to get off of 2016 on our laptops.

Thank you!

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices