Don, the latest image on Dockerhub for CF2021 is indeed update 12. You can see it on the site (https://hub.docker.com/r/adobecoldfusion/coldfusion2021/tags), or of course you can pull it:

docker pull adobecoldfusion/coldfusion2021:2021.0.12

If you might be instead running images using adobecoldfusion/coldfusion2021:latest do beware that until you do a PULL of that, you will continue to run whatever WAS the latest version when you last did a docker pull of that image (with the latest tag, or with no tag at all which then presumes to give you the then-latest). Indeed, if you do that last pull now (of adobecoldfusion/coldfusion2021:latest) you will ALSO get update 12 (until later updates come out).

BTW, if you ever wonder about a CF image version (and the tag doesn't tell you), you can always confirm what update you are on by running the image at the command line with its "info" argument, as discussed on that dockerhub page above, or in the CF Docker image docs (linked to also from that page).

Let us know if this gets you going.

JCC, Adobe typically will not respond publicly to questions of clarification about licensing--especially when as in this case you are looking for more precise definition of what they mean by cores and compared to "virtual cores". They would point you first at the EULA (just google ColdFusion EULA), and the couple of paragraphs on that there.

And FWIW, one thing that is stated clearly there (and can be stated clearly here) is that CF Standard is licensed per 2 cores, while Enterprise is licensed per 8 cores. 

When people want more specifics than that, they always direct you to speak to someone on the CF team (where the answer is only ever private, sadly). And you can send such a question to cfinstal@adobe.com, which is the address for free installation support. They would get your question to the right people, who would get back to you.

If YOU then want to come back and share what you learn, I don't think you're asked to sign any NDA to hear their answer. 🙂 But there are often subtle differences between what one person is asking and another, even for what may seem "the same question". There are also differences (sometimes) between what one version of CF will say in its EULA, and another. I think those are additional reasons why Adobe tends never to answer questions like this publicly. But they could prove me wrong.

Hope that helps, in the meantime.

While you await any reply from Adobe, John, I'll note first that (as you may know) they don't tend to make announcements in advance of whether (let alone when)  they may be adding support for a new version of such a thing. But they may, so it's worth asking. 🙂 

Some "good" news is that when it comes to such things as new versions of dbs, OSs, web servers, or other integrated things, they do tend to get there eventually. We just have to wait. 🙂 

But, sure, some people can't or won't wait, and want to proceed ahead. At least with dbs, there are a couple of options.

First, sometimes if we point to a new db version with our existing cf dsn (and its underlying driver), things will just "work". But this is indeed where Adobe will list in that document what is known to work. 

Second, often that is referring to the jdbc drivers that Adobe provides which in the case of things like sql server, oracle, and others is about drivers they have licensed from Data Direct/Progress. In that case, it's really up to them Progress first to update the driver, then for Adobe to get and provide it in a cf update. 

But when it comes to postgres, as you may know later versions of cf provide a driver (and a postgres option in the cf admin dsn driver types). And while you could replace that driver (and it may work), there's still another option some may propose.

And it can be considered by anyone wanting to use an updated driver for any db. As you may already know, John (and I'm adding this as much for others), cf has long offered the option to configure an "other" jdbc driver type, when setting up a dsn.

That can be used with literally ANY jdbc driver and thus any database and version. Folks interested in that can see the cf docs (or any of many blogs) that talk about using that "other" driver option. Granted, there may be little on postgres specifically, but the steps are generally the same regardless of the db.

But one gotcha with postgres is due to the fact that later versions of cf come with their own postgres driver. That's nice. And technically you CAN get a new driver, but you can't have two versions of the same driver implemented in cf at once, meaning different versions of the same jar. There's no way for this "other driver" feature in cf to point at a different specific version than the one cf came with.

So that's where your plan to just drop in a new driver jar (and use the "postgres" dsn option) may be best. It's not formally supported to replace the jar (that I know of), but it may work. 

(For those curious, this wouldn't have come up in the last with the other cf builtin data direct db drivers because they were always too expensive for anyone to obtain and try to use a "newer" one.) 

Anyway, I realize you were  asking if anyone may well have done any of this with pg12 and had any experience to report. I'll say I have none to share. Perhaps others may report that here.

But really, you may do better on that by opening a specific question here in the cf forums, as they may not see this comment in this thread. You could then offer a link to it here, or maybe share a thought here later on how things went.

Hope that's helpful. I know it's more than what you sought, but the recent change in cf supporting postgres does change things a bit, and I thought others may benefit from thinking it through a bit.

I just followed those links, and I see only CF2021. You may be experiencing browser caching issues. 

Indeed, as for not getting the file downloaded once you DID fill out the form, I have experienced that as well (and yes, I mean even when I DO see the page offering CF2021). It seems to be a cookie issue. As soon as I open a new incognito window (in Chrome, or a private Windows if using Firefox), then it DOES work--each time. Frustrating yes, but doesn't happen to everyone, and at least this is a solution until some better ultimate solution is implemented by Adobe.

And as for that last URL downloading the 2018 "express" edition, indeed it does. That link is NOT offered on the 2021 version of that page. That's a further indication that you are seeing a cached version of the page where you DID see that.

Can you try an incognito or private window, or another browser entirely (than what you are now using), to see if that solves things? Again, I appreciate how frustrating all this is. I don't work for Adobe, so can't do any more than offer help here. (Maybe someone from Adobe will respond with a different answer, of course. Just trying to help you until then.)

Nope, Enterprise is per 8 cores, while Standard is per two, as stated in the eula and in the faq when I looked last week, after the release, and it had been updated for 2021.

Might you have been looking in the standard part of the faq? If you feel not, please do quote the text and offer a link where you saw it. Thx

Hi Carl,

SQL 2019 is supported. We shall update the support matrix. Thank you.

neochad, you're confusing CF Builder. THAT is what is listed only as a 2018 version. You can no longer get CF2018 anywhere on the Adobe site (unless you have a license and get it from the licensing.adobe.com site)

So when you ask how to get the Dev edition of CF2021, it's the from the same page you can choose to get either the trial or to buy CF, the CF "product family" page. The easiest way to get to it/remember it, use coldfusion.com. There are sections on that page for the various "editions" of CF, and buttons to start the process to download them.

Does that get you going?

Thanks a lot Charlie for your feedback. We're working on it and will update this thread.

Thanks,

Saurav