[Looking for Charlie's main web site?]

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:

"Using Adobe's "new" CFSetup tool to manage CF Admin settings for ANY CF version"

You may (or may not) have heard that CF2021 added (in 2020) a new command-line tool called CFSetup--but first, did you know that it could be used with ANY CF version, not just CF2021? And perhaps you heard its main value is to export/import CF Admin settings via JSON: it can indeed do that, and while that may excite some, others may yawn if they've "seen that elsewhere". (To be clear, it can export/import either ALL settings or selected ones.)

But did you know it could be used for far MORE than that alone? And did you know that those exported json config files could be used to set the admin configuration on startup of CF 2021 Docker images. Even if not using Docker, the tool can be a boon for all sorts of automated deployment of CF--again any CF version. And did you know you don't even need to install CF2021 to use it?

While the feature is well-documented (and offers its own help), who has time to read the docs, right? In this session, veteran CF troubleshooter Charlie Arehart will present and demonstrate the key capabilities of CFSetup, as well as others that may surprise you. He'll also conclude with a brief discussion of the similar (but different) tool, CFConfig, a plugin for Ortus Commandbox. He'll touch on the question of why one might choose one over the other (it's ok to use either or both with the same CF instance). He'll also contrast these with the much older CF "CAR" Admin migration tool. Each tool has its value for different needs.

As always with the CFMeetup, anyone can attend, viewing it live or afterward on youtube. You can also register (indicate interest) or find more details about the event and about the meetup itself at the CFMeetup event page.

As noted there, all sessions are recorded, with those since 2015 available as a youtube playlist. Of course, we welcome anyone presenting any topic that may be of interest to the CF community.

Calling all CF Summit speakers: consider presenting your sessions

Indeed, since Adobe will not be recording the sessions at CF Summit (due to technical and union challenges), I hope to get those presenters to offer their session after the event which is next week.

Finally, this talk of mine on the CFSetup tool forms a useful foundation for part of what I will be presenting myself next week at the CF Summit on how the Adobe CF Docker images have evolved. More on that in this post.

But this talk on CFSetup stands alone, and I hope that many people may be surprised and delighted to learn of the tool, and especially how it can be used with ANY version of CF--even without having CF2021 installed. The fact that the exported json can be used to configure Adobe CF Docker images is icing on the cake. (And yes, yes, there is totally different "icing" in the form of Commandbox CFConfig. As I noted above, I will contrast the tools briefly in my talk. The focus is on CFSetup, though, which doesn't get anywhere near the attention of CFConfig!)

For more content like this from Charlie Arehart: Need more help with problems?
  • If you may prefer direct help, rather than digging around here/elsewhere or via comments, he can help via his online consulting services
  • See that page for more on how he can help a) over the web, safely and securely, b) usually very quickly, c) teaching you along the way, and d) with satisfaction guaranteed
Charlie, thanks for all the information over the years for supporting and implementing ColdFusion. I'm moving our server version of ColdFusion 2016 to Docker Coldfusion 2023.

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?
Eric, first, thanks for the kind regards. But second, well, I never thought I'd quote Scott Stroz' famous line (from the old CF podcast he used to co-host), but it may well be "you're doing it wrong". :-)

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.
I have 2 enterprise licenses and I want to run two servers with those licenses. Will that consume both licenses If I run two containers with the same license?

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:
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.
# Posted By Eric Seibert | 4/29/24 3:26 PM
Adobe's licensing for cf containers is indeed rather obtuse, but the good news is that according to the info available (a faq, not the EULA), each cf enterprise license can run 8 containers (while a cf standard license can only run one). So your set..but this does not mean you can use a given cf enterprise license for BOTH a real machine AND containers. It's either/or, but since you have two licenses, you could use one for all your container needs and one for some real machine.

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:

Copyright ©2024 Charlie Arehart
Carehart Logo
BlogCFC was created by Raymond Camden. This blog is running version 5.005.
(Want to validate the html in this page?)

Managed Hosting Services provided by
Managed Dedicated Hosting