Blog

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: 

https://commandbox.ortusbooks.com/config-settings/misc-settings#tabcompleteinline

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:

https://commandbox.ortusbooks.com/embedded-server/single-server-mode

Release Notes

Here are the release notes for the 5.2.1 release.

Bug

  • [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

Improvement

  • [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 commandbox.properties 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

(1)

Jan 09, 2021 22:51:29 UTC

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

Ortus Solutions Returns to CFCamp as Platinum Sponsor – Join Us to Redefine the Future with BoxLang!

Ortus Solutions Returns to CFCamp as Platinum Sponsor – Join Us to Redefine the Future with BoxLang!

We’re thrilled to announce that Ortus Solutions and BoxLang will once again join CFCamp as Platinum Sponsors for the 2025 edition. As passionate advocates of innovation in the CFML and modern JVM space, we’re proud to keep pushing boundaries—and this year is shaping up to be our biggest presence yet.

Day 1 Keynote by Luis Majano

CFCamp 2025 will kick off with a keynote delivered by none other than our CEO and BoxLang creator, Luis Majano. Join...

Cristobal Escobar
Cristobal Escobar
April 25, 2025
Must-See Into the Box 2025 Sessions for CommandBox Users!

Must-See Into the Box 2025 Sessions for CommandBox Users!

Power Up your CommandBox experience and practices at Into the Box 2025

Want to get hands-on with the new CommandBox features or learn how others are pushing it to the next level? These are the must-see sessions at ITB 2025 if you're a CommandBox user:

Maria Jose Herrera
Maria Jose Herrera
April 21, 2025
Must-See ITB 2025 Sessions for TestBox Users!

Must-See ITB 2025 Sessions for TestBox Users!

Are you a fan of TestBox or looking to level up your testing game in 2025? Whether you're just getting started with unit testing or you're already building advanced specs for ColdBox and BoxLang apps, Into the Box 2025 has an exciting lineup tailored just for you. Into the Box 2025 has an exciting lineup tailored just for you. With the recent launch of TestBox 6.3.0 we have amazing new tools, features and tips and tricks to get your testing experience to the next level, review our sessions and test like a pro efficiently and easy!

From hands-on testing strategies to BoxLang innovations, here are the sessions you won’t want to miss this May — and why they matter to you as a TestBox user.

Maria Jose Herrera
Maria Jose Herrera
April 17, 2025