Adobe released ColdFusion 2021 this week. It's a pretty big release with a modularization of the core engine and a nice list of language enhancements.
Here's what you need to know for using it with CommandBox.
The 2021.0.0 version is already on ForgeBox. If you're thinking, "Hey, wasn't this version 2020?" you'd be right. It got...changed at some point recently. You can start an ACF 2021 server just like any other Adobe server right now like this:
CommandBox> server start cfengine=adobe@2021
We've only done basic testing, but the server seems to start up just fine. Check the server log, or do a --debug start if you have any issues.
server log server start --debug
If you're using CFConfig, you'll need to update it to the latest version so it recognizes the version.
CommandBox> update --system
We haven't added any new settings to CFConfig yet, so it you find some new 2021 settings you need to be able to import/export please let us know what they are.
Following in the footsteps of Lucee 5, ACF 2021 uses OSGI bundles to load/unload additional functionality into the server. This makes the core engine a lot smaller, but it also means your app may not compile until you've added in some missing pieces. Unlike the default Lucee server that ships with most extensions, Adobe CF 2021 ships with almost no extensions. We're still discussing how to handle this in ForgeBox.
For Lucee, I have two ForgeBox slugs: lucee and lucee-light. The former coming with most extensions and the latter coming with none. We've considered adding additional options to download an Adobe engine with all the same functionality that previous versions had. However, I'm not sure if time is better spent putting effort into making it easy to declare your needed packages and just let CommandBox automatically install those packages for you.
The ColdFusion Package Manager, or cfpm is a tool that ships with ACF 2021 in the form of a script in the cfusion/bin folder you can run to download and install additional functionality into your server. Unlike Lucee, ACF 2021 doesn't appear to have any file system based convention whereby you can download these packages manually, place them in a special deploy folder, and have the engine just slurp them in. It seems the installation needs to flow through the cfpm script.
You can run cfpm from inside CommandBox like this. It works well, but it's not pretty.
!C:/Users/Brad.development/Documents/GitHub/cfconfig/tests/resources/adobe2021/serverHome/WEB-INF/cfusion/bin/cfpm.bat install feed
As such, I've added a new feature to the latest CommandBox 5.2.0-RC.1 build to make it easier for you to call the cfpm tool without needing to dig into the bowels of your server installation to find it. CommandBox now has a top level command called "cfpm" that, when run in the webroot of an Adobe 2021 server, will find the location of the cfpm.bat or cfpm.sh script and execute it, passing along any parameters you supply
// This opens the cfpm shell. Type "q" and hit enter to exit back to CommandBox CommandBox> cfpm // This directly runs a cfpm command CommandBox> cfpm install feed
This should make life a little easier while we work on a better convention for CommandBox to "auto-install" packages from your box.json or server.json file on server start.
Remember, you need to update to the CommandBox 5.2.0 build to get this feature.
If your a ColdBox or TestBox user, you may run into issues. ColdBox 6's app templates don't appear to run at all on CF 2021 and we've heard reports of TestBox not working as well.