I'll be presenting at the online CFMeetup, on Adobe's 'new' CFSetup tool, useful for any CF version
This topic may (should) interest folks using CF2021 or even OLDER CF versions. Did you know there's a command line tool to help view/manage as well as export/import CF Admin settings? I will be presenting a talk on this, Thursday. Anyone can attend online.
Folks who are members of the Online ColdFusion Meetup that I run will already have gotten notification about this, but those who are not:
My site has 3 instances running including the cfusion and 2 others. Installing the base cfusion isn't difficult, but I'm running in to an issue of creating the other two instances int he same ColdFusion container. Using cf2016 I exported the .car files and I can mount them in a directory, but I want to create and launch the the two instances when the container is built.
I suspect the right answer is to use the car files and a cfsetup script to provision the other two instances but I'm having difficulty doing that. If I put the car files in my /data it wants to load that to the cfusion instance.
I', not able to use commandbox or lucee presently but I have looked somewhat exhaustively at loads of documentation and have yet to find anything that outlines setting up multiple cf instances on the same container.
How do I go about getting the server admin configs from 2016 into a json file that I can refer to in a cfset2023.cfm script?
It would not really make sense to run multiple instances within a single CF container. The whole idea of containers is that each should do one thing. Now, COULD one? I suppose it's possible, but it's not really within the ethos of containers, where there's only one process that should be started at the launch of the container. (You'd have to shoe-horn a way to launch the processes for the other instances.)
Instead, you should split your instances into each being their own container. I suspect you have a reason to think that's not what you want to do. Tell us more.
Of course, this is really outside the scope of this blog post--though I realize you felt it was reasonably related as you were asking how you could solve this with cfsetup.
As for the CF image's ability to load either CAR files or cfsetup json at container startup), those definitely WILL only work with the one cfusion instance. Again, the CF images have no provision for running multiple instances (even if one found a way to "force it").
So really, I hope you'll instead split your instances into their own containers. That would be better for many reasons. Let us know how it goes or if you have more questions.
Our current setup is:
two AWS ec2 servers clustered for HA with one license on each server.
Each server has ColdFusion2016 and with 3 cfinstances/apps:
cfusion
apps
webapps
Apache handles the traffic requests via proxy config.
I need to replicate the structure in the upgrade from cf2016 server-based to an AWS ec2 instance container-based running docker coldfusion:latest (2023).
I did as you suggested and split the instances
If both licenses won't be consumed that's fine I can run the instances, and integrate fusionreactor, and pmt and all the addons. If both licenses are consumed I can't configure clustering for HA.
I plan to use AWS ELB to direct traffic to the applications and to the cfadmin for each container. I'd like not to use apache or nginx if possible and let the default built-in server handle the http/https request.
Anyway, this is how I read things. You can see it for yourself, via a blog post I did on the Adobe CF portal some years ago pointing this out and linking to the faq:
https://coldfusion.a...