CommandBox 5.2.1 Release

Brad Wood December 17, 2020

Spread the word

Brad Wood

December 17, 2020

Spread the word

Share your thoughts

Today we are announcing the release of CommandBox 5.2.1.  This is a patch release for 5.2.0 that fixes a few small regressions and adds a few features.

Notable Changes

There is now a new "forgebox logout" command you can use for testing or just to remove your API token from the local CLI.

# Logout one user
forgebox logout username

# logout all users
forgebox logout

You can change CommandBox's default tab completion to be an inline list that follows your cursor. This setting requires you to close and re-open the shell to take affect.

config set tabCompleteInline=true

Read more here:

We've added better debugging information for Server Profiles.  If you add the --verbose flag to your server start, you'll be able to see what profile was detected for your server, and what baked-in rules have been turned on as a result.

   | √ | Setting Server Profile to [development]
   |   |------------------------------------------------------
   |   | Profile set from "environment" env var
   |   | Block CF Admin disabled
   |   | Block Sensitive Paths enabled
   |   | Block Flash Remoting enabled
   |   | Directory Browsing enabled
   |   |------------------------------------------------------

We've added a new Single Server Mode you can enable in the CLI to make using CommandBox in Docker images easier.

Read more here:

Release Notes

Here are the release notes for the 5.2.1 release.


  • [COMMANDBOX-1231] - Installing via lex endpoint uses incorrect file extension
  • [COMMANDBOX-1232] - Location of predicate file is in a folder that the Docker finalization script deletes
  • [COMMANDBOX-1238] - Command alas for run command doesn't expand properly

New Feature


  • [COMMANDBOX-1227] - verbose server start output for profile and security settings
  • [COMMANDBOX-1228] - Extend ${} scopes to apply to any getSetting() call or "env show" command
  • [COMMANDBOX-1229] - Modules aren't unloaded on reload or shutdown
  • [COMMANDBOX-1233] - Add debug output that shows location of file on start
  • [COMMANDBOX-1234] - Add single server mode for CommandBox in a Docker container
  • [COMMANDBOX-1236] - Add Testbox runner to sensitive paths in production profile
  • [COMMANDBOX-1241] - Use UTF-8 when reading files with "cat" command

Add Your Comment


09 Jan 2021 10:51 PM

by Douglas Cohn

Hi Brad, Are there any plans to do this type of image for Azure? I was led to believe if running a lot of Windows VMs Azure is a better choice especially with monthly fee of the Windows Server at Amazon versus Microsoft. I finally have management looking very seriously to using Lucee and the question that comes up is why use CommandBox to run Lucee versus installing Lucee directly on a Server 2019 VM. I was under the impression that Command box is much easier to pick up the whole environment and drop it on another server. I also thought that CommandBox was great at managing the updates and along with the service piece can be used for Production as well. Production is why we have been looking at it. That said what is the advantage of installing CommandBox for a Lucee production server in Windows Server 2019 versus installing Lucee directly on the VM. Recently the dev started looking at the server we had setup for a Commandbox and he said his code broke because Lucee was updated. I had thought I locked the configs to a specific Lucee version. When I looked at the config Lucee was locked but at a major version. The upgrade was .92 to .95 I believe. Lucee 5.3.5 and I assume the minor version update was possible. But break code and lose all his DSNs sure seems odd to me. "app":{ "cfengine":"lucee@5.3.5" Have a great day/night weekend Doug

Recent Entries

CommandBox 5.4.2 Released!

CommandBox 5.4.2 Released!

There is a new update for CommandBox CLI available.  Version 5.4.2 is a patch update that contains a few bug fixes including two important ones. 

  • There is a fix for a regression introduced in 5.4.0 where updating the version of a CF engine doesn't work without forgetting the server first. 
  • There is also an important security impro...

Brad Wood
Brad Wood
October 07, 2021
ContentBox v5.x Released

ContentBox v5.x Released

We are incredibly excited to announce the release of the ContentBox Modular CMS v5 series. This has been a work over 1 year with a complete refocus and rearchitecturing of the core to take ContentBox to the next 10 years. It is also great to note that we are Professional Open Source, FREE, FOREVER. This series includes tons of great features and updates that will take your content management to the next level. From multi-site support, a companion CLI, to a complete Headless CMS deployment, your will be able to deliver your projects in no time. We have also refreshed the official ContentBox site: which is also running 5.

Here is our what's new guide with our full release notes:

Luis Majano
Luis Majano
September 29, 2021
Adobe to Sponsor Into the Box 2021!

Adobe to Sponsor Into the Box 2021!

It is with great honor that we announce Adobe’s support as a Gold Sponsor for this year’s Into the Box.  Their backing has been key in ensuring the success of our events in both the United States and Latin America. 

Paulina Lainez
Paulina Lainez
September 22, 2021