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 a CommandBox 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, and postFoo, 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:

"scripts":{
  "preVersion":"testbox run",
  "postVersion":"package set location='gituser/repov#`package version`'",
  "postPublish":"!git push --follow-tags"
}

Then when you want to publish a new version of your package, commit your changes to Git and run the following commands:

bump --minor
publish

Those two commands, in combination with your package scripts, would accomplish the following:

1. Run the package's test suite (a failure will abort the process)
2. Increase the minor version of the page
3. Tag the Git repo
4. Change the package's location property in box.json to point to the new tag
5. Commit the tag and new box.json
6. Publish the package to ForgeBox
7. Push the new box.json and Git tag

onInstall interceptor/package script

Announced while a package is being installed, after the package endpoint and installation directory has been resolved but before the actual installation occurs. This allows you to override things like the installation directory based on package type. Any values updated in the interceptData struct will override what the install command uses.

CLI Engine Update

The Lucee version that the CLI runs on has been updated to be 4.5.3.020 which is also now the default engine to be used when you use the "server start" command and don't specify a cfengine.  If you still want to start a web server on Lucee 4.5.2.018, then simply to this:

start cfengine=lucee@4.5.2+018

Release Notes

There are tons of little bug fixes in this version that you can view in our release notes.  

Bug

• [COMMANDBOX-187] - error when updating forgebox when slugname changes
• [COMMANDBOX-422] - Empty command CFCs with no functions throw an error starting box
• [COMMANDBOX-423] - Error "key [FUNCTIONS] doesn't exist" thrown when trying to start command box
• [COMMANDBOX-426] - server name completion errors on server open command
• [COMMANDBOX-434] - Document the resolvePath() differing behaviour on OSX vs Windows
• [COMMANDBOX-435] - artifacts clean fails on OSX when there's .DS_Store files
• [COMMANDBOX-437] - appSkeleton in the coldbox create app wizard needs to comply to IDs instead of local disk
• [COMMANDBOX-449] - "server open" always opens localhost
• [COMMANDBOX-451] - The trayicon in server.json does not work with relative paths
• [COMMANDBOX-464] - update command doesn't respect original install path
• [COMMANDBOX-465] - custom url rewrite location doesn't respect starting server by name in different location
• [COMMANDBOX-466] - coldbox create crud doesn't work on Windows

New Feature

• [COMMANDBOX-316] - Add Fusion Reactor support for server
• [COMMANDBOX-399] - Starting server in web root with WEB-INF treats CWD as war
• [COMMANDBOX-416] - Add "open" flag to touch/new command.
• [COMMANDBOX-430] - forgebox whoami command to show what user your API key is set to
• [COMMANDBOX-431] - Update the storage of the APIkey in the commandbox settings to include multiple keys
• [COMMANDBOX-432] - Have a forgebox use {username} command to switch the current api key
• [COMMANDBOX-445] - Allow aliases (virtual directory) in web server
• [COMMANDBOX-458] - Provide custom 40x and 50x error pages for servers

Improvement

• [COMMANDBOX-398] - Catch error scenario when user tries to start a server with a WEB-INF
• [COMMANDBOX-410] - Upgrade to latest Runwar with several bug fixes
• [COMMANDBOX-412] - Refactor string similarity to use external library
• [COMMANDBOX-413] - Refactor semver CFC to be separate lib
• [COMMANDBOX-414] - Refactor path pattern matcher CFC to be separate lib
• [COMMANDBOX-419] - coldbox create app command does not list all templates
• [COMMANDBOX-420] - Run pre/post package scripts by convention
• [COMMANDBOX-421] - Add onRelease interception point/package script
• [COMMANDBOX-424] - Serious performance issue with formatting large JSON strings
• [COMMANDBOX-425] - Better handle syntax errors in a module's config
• [COMMANDBOX-427] - Move onServerStart interception announcement to have server home dir
• [COMMANDBOX-428] - Allow tray options to be customized
• [COMMANDBOX-433] - Add onInstall interception point
• [COMMANDBOX-436] - Incorrect custom model path in the unit test
• [COMMANDBOX-440] - Exit REPL multi-line with extra enter stroke
• [COMMANDBOX-442] - Don't use in-use port specified in start params or server.json
• [COMMANDBOX-443] - Wait for full debug output when starting server with debug=true
• [COMMANDBOX-444] - Append JVM args and runwar args to server defaults
• [COMMANDBOX-454] - Update to Runwar 3.4.10
• [COMMANDBOX-457] - Improve server status detections
• [COMMANDBOX-460] - Show tag stack when executing .cfm files
• [COMMANDBOX-461] - Improve tab completion of forgebox slugs
• [COMMANDBOX-467] - Allow custom images inside tray menu plus disabled items
• [COMMANDBOX-468] - Add overwrite confirmations to all coldbox create commands
• [COMMANDBOX-469] - Improve version output in "forgebox show" command
• [COMMANDBOX-470] - Upgrade engine to Lucee 4.5.3.020

We've updated ForgeBox.io to have updated CF Engines for Adobe ColdFusion as well as Lucee Server to include some recent security fixes from each as well as some new yet-to-be-released Lucee features.

Here are the new Adobe ColdFusion versions:

• ColdFusion 11 Update 21 (10.0.21+300068)
• ColdFusion 11 Update 10 (11.0.10+300066)

Here are the new Lucee Server versions

• Lucee 4.5 Stable (4.5.3+020)
• Lucee 5.0 Stable (5.0.0+254)
• Lucee 5.0 Snapshot (5.0.1-snapshot+067)
• Lucee 5.1 Beta 2 (5.1.0-beta.2+031)

We are excited to announce we have joined !

Sponsor Us
 

At Ortus Solutions we are known for building open source projects for the ColdFusion (CFML) community such as ColdBox, CommandBox, ContentBox Modular CMS, ForgeBox and many more. All of those products are licensed under the Apache 2 license and are completely FREE to use and extend.

 

However, the amount of effort needed to maintain and develop new features for all projects is not sustainable without proper financial backing. This is where you can come in and help support Ortus Open Source Software by pledging on Patreon. We have listed a bunch of options for you to sponsor Ortus Open Source Projects with lots of rewards like getting awesome recognition and some great discounts, swag and t-shirts. By pledging as little as $10 a month, you can contribute to this great cause and allow Ortus Open Source to have faster and ongoing development cycles. Pledge more and you can even be part of our product roadmap planning sessions.

 

If you run a business and are using Ortus Open Source software in a revenue generating product or service, it makes sense to sponsor Ortus Open Source Software development: it ensures the project that your product/services use stays healthy and actively maintained. If you are an individual user and have enjoyed the productivity of our Open Source Software tools, consider donating as a sign of appreciation :).

Sponsor Us
 

We are happy to announce the immediate availability of CommandBox 3.2.0 to the public. This is a minor release of the CLI tool and aimed at adding some polish to the multi-server features that came out in 3.1. Jon Clausen also worked to get the latest Adobe 10, 11, and 2016 updates added to ForgeBox as well so you can start up Adobe servers with all the latest fixes.

I hope you are enjoying Ortus Solutions' ContentBox Roadshow so far. We're had one free webinar already, and a few blog posts, with plenty more to come. Today I'm going to talk about modules a little more. I mentioned them in my "What's New with ContentBox" presentation ( you can read more about it and watch the recording here  ), but you might not have known, I got excited about ContentBox and all of the modules before the roadshow even started.

We are pleased to announce the general availability of CommandBox 3.1.1 Final.  This is a minor release of our CLI tool,  but with some major new features.  We actually made the final 3.1.1 builds public a couple weeks ago for Into The Box, but have just now finalized the documentation and press release.  

In previous posts we have talked about creating a ColdBox module from scratch ( ContentBox - Extending ContentBox 3 with your Own Custom Modules ), one file at a time, to see the minimum files required to make the module work. That was a great educational exercise, but lets look at another way to create a module, with CommandBox's ColdBox scaffholding commands. 

In the last blog post, we talked about extending ContentBox with modules. With ContentBox being built on top of ColdBox, and integration with ForgeBox using CommandBox, there are a lot of modules ( and module locations), and how those modules interact isn't obvious at first. To be honest, with ContentBox 3, we only just decided to move the core contentbox modules, to provide clearer separation, and easier source control management... things are changing, so I thought this would be a great time to explain about the different type of module locations, and why you should use one over another.

We recently announced the availability of CommandBox 3.1.0 beta for testing.  We've make a screen cast also showing how to start Adobe, Lucee 5, and Railo servers which you can view here.  We've also prepared this short screencast that shows how you now interact with the new ForgeBox 2.0 API via your command line to create users, and publish packages.   Check it out below.

https://www.ortussolutions.com/blog/commandbox-v310-beta-ready-for-testing

We recently announced the availability of CommandBox 3.1.0 beta for testing.  We've also prepared this short screencast that shows starting up Adobe, Railo, and Lucee 5 servers in CommandBox.

If you'd like to see more, please check out our official announcement blog that overviews all of the CommandBox 3.1.0 beta features.

https://www.ortussolutions.com/blog/commandbox-v310-beta-ready-for-testing