CommandBox 3.3.0 Released - server enhancements and bug fixes

Communities CommandBox CLI
1

https://www.ortussolutions.com/blog/commandbox-330-released-server-enhancements-and-bug-fixes

Full release notes are available in the link above:

We are pleased to announce a minor release of our CommandBox CLI, server, and package manager tool today. Version 3.3.0 of CommandBox is our second minor release since we added support for starting Adobe ColdFusion engines, Railo, and Lucee 5 web servers. This release has 46 tickets that focus on cleaning up more rough edges around the server implementation, adding features, and of course, fixing bugs. A big thanks to Denny Valiant and his work on Runwar, which is the library that makes CommandBox’s severs work.

Download it

You can download the latest binary from our CommandBox product home page:

CommandBox Download

We’ve also updated our CommandBox documentation book to cover all these new features which can be found here:

CommandBox GitBook Documentation

Remember, you can send pull requests via Github for any typos or missing content you find in our GitBooks!

The Command API Docs also show the latest commands and usage too:

CommandBox Command API Documentation

What’s New?

Let’s take a quick peek at the major new features in CommandBox 3.3

Server Enhancements

The embedded CommandBox server have seen a number of nice enhancements to make it easier for you to use CommandBox for super easy local development.

Fusion Reactor Module

The more people begin to use CommandBox for local development, the more interested they became in being able to run FusionReactor on their dev servers to help trouble shoot their code. That’s why we created aCommandBox FusionReactor module. It’s not part of the core, but can be installed in a single command and will attach FusionReactor’s server monitor to every server you start. You’ll need to have a FusionReactor license or sign up for a trial to use it.

install commandbox-fusionreactor
fr register "your FR license key"
server start
fr open

Web Aliases

CommandBox allows you to create web aliases for the web server that are similar to virtual directories. The alias path is relative to the web root, but can point to any folder on the hard drive. Aliases can be used for static or CFM files. To configure aliases for your server, create an object under web called alises. The keys are the web-accessible virtual paths and the corresponding values are the relative or absolute path to the folder the alias points to.

Here’s what your server.json might look like.

{
  "web" : {
    "aliases" : {
      "/foo" : "../bar",
      "/js" : "C:\static\shared\javascript"
    }
  }
}

Here’s how to create aliases from the server set command:

server set web.aliases./foo = bar

Custom Error Pages

You can customize the error page that CommandBox servers return. You can have a setting for each status code including a default error page to be used if no other setting applies.
Create an errorPages object inside the web object in your server.json where each key is the status code integer or the word default and the value is a relative (to the web root) path to be loaded for that status code.
This is what you server.json might look like:

{
  "web" : {
    "errorPages" : {
      "404" : "/path/to/404.html",
      "500" : "/path/to/500.html",
      "default" : "/path/to/default.html"
    }
  }
}

You can set error pages via the server set command like this:

server set web.aliases.404=/missing.htm

Custom tray menu items

You can customize these tray menus and add your own option for your convenience. To add a menu contribution to an individual server, add the following to your server.json:

{
  "trayOptions":[
    {
      "label":"Foo",
      "action":"openbrowser",
      "url":"http://${Setting: runwar.host not found}:${Setting: runwar.port not found}/foobar.cfm",
      "disabled":false,
      "image":"/path/to/image.png"
    }
  ]
}

Tray menu makeover

We’ve updated to a new library that creates the tray icon for your running servers and the menu that appears when you right click. In addition to better support for some Linux distros, we’ve added some nice new icons to the menus.

Pre/Post package scripts

Before any package script is run, CommandBox will look for another package script with the same name, but prefixed with pre. After any package script is run, CommandBox will look for another package script with the same name, but prefixed with Post. So if you have a package that contains 3 package scripts: foo, preFoo, andpostFoo, they will run in this order.

  1. preFoo
  2. foo
  3. postFoo

This works for built-in package script names as well as as doc package scripts. It also works on any level. In the example above, if you created a 4th package script called prePreFoo, it would run prior to preFoo.

Better ForgeBox Login management

If you use more than one ForgeBox login, perhaps a personal one and a company one, it can be a pain to keep logging in. It’s also hard to remember the last user you logged in with. We’ve introduced two new commands to help with this. Run this to tell you who you are logged in as:

forgebox whoami

Run this to switch between users that you’ve previously logged in with:

forgebox use myUser

onRelease interceptor/package script

We’ve added a new “onRelease” interceptor and package script to help with the workflow of publishing packages. Here’s a run down of the three key points when bumping a package version.

  • preVersion - Announced before the new version is set using the bump command
  • postVersion - Announced after the new version using the bump command but before the Git repo is tagged.
  • onRelease - Announced after a new version is set using the bump command and after the Git repo is tagged.

Here is a typical package script work flow for working with a package that’s hosted on GitHub and published to ForgeBox: