The Ortus BlogBox

"Ortus: A rise, beginning, coming into being, born, the origin!"



Category Filtering: 'releases'


ColdBox 4.3.0 Released

Luis Majano
Oct 19, 2016


We are pleased to announce the general availability of ColdBox 4.3.0, WireBox 4.3.0, CacheBox 4.3.0 and LogBox 4.3.0. This is a minor release with some great improvements and lots of bug fixes. So let's look at the major things in this release.

CacheBox, ColdBox MVC, ColdFusion, CommandBox, News, Releases, WireBox 0

CommandBox 3.3.0 Released - server enhancements and bug fixes.

Brad Wood
Oct 09, 2016


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:

      "url":"http://${Setting: not found}:${Setting: runwar.port not found}/foobar.cfm",

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:

  "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

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 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, 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.  


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


CommandBox, News, Releases 0

ContentBox 3.0.0 is Released - The wait is over

Gavin Pickin
Aug 02, 2016


We are happy to announce, ContentBox 3.0 FINAL is now available to the public. After a lot of hard work, we are finally ready to cut the release. With 100+ issues included in this release, this major release is nothing short of massive. With ColdBox 4 updates, Theme updates, Enterprise updates, Security Updates, JSON Support and Exports, Native Markdown Support, Autosave and much more, this major release has something for everyone. ContentBox 3.1.0 is already in development as well and can be installed via CommandBox using the contentbox@be Identifier.

Alongside the release we have many other announcements around the CMS. So get ready!

ContentBox CMS, Releases 0

CommandBox 3.2.0 Released plus new Adobe Servers on ForgeBox

Brad Wood
Jul 21, 2016


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.

CommandBox, News, Releases 0

CommandBox v3.1.1 Released

Brad Wood
Jul 01, 2016


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.  

CommandBox, ForgeBox, Releases 0

CFCouchbase SDK v2.0.0 Released

Luis Majano
Jun 10, 2016



More than two years have passed since CFCouchbase 1.1 was released. With community support, we are happy to announce the release of CFCouchbase 2.0.0! If you are not familiar with CFCouchbase we encourage you to checkout the Documentation. The SDK has been updated to support the new functionality available in Couchbase Server 4.x, including:

  • N1QL Queries
  • GSI Indexes
  • Replica Reads
  • Document Locking
  • Prepared Statements
  • Improved Design Document Management
  • Expanded Configuration Options
  • And more…
CFCouchbase, Releases 0

Introducing ColdBox Elixir: UI Asset Manager

Luis Majano
Jun 07, 2016



We are very excited today to formally announce the availability of ColdBox Elixir, coldbox/elixir. ColdBox Elixir provides a clean, fluent API for defining basic Gulp tasks for your ColdBox applications.


This project was forked from the Laravel Elixir project, so many many thanks for all their hard work and ideas.



We wanted to provide ColdBox developers and easy way to approach an asset pipeline and task executor. The elixir project accomplished this and we have extended it to match the conventions used in ColdBox but also took it a step further to make it compatible with TestBox and CommandBox. This way you can have a full task runner available to you than can integrate with CommandBox recipes, package management, command execution and also TestBox executions.

ColdBox MVC, ColdFusion, Elixir, Releases 0

ContentBox ColdFusion CMS v3.0.0 Release Candidate is here!

Luis Majano
May 23, 2016



We are so excited to bring about the release of ContentBox 3.0.0 Release Candidate to you today. It has been a monumentus milestone for us at Ortus Solutions as we have devoted almost a full year's worth of development, which has been unusual for our releases, but so worth it for ContentBox ColdFusion CMS.

This release candidate is a major release and with a completely rewritten administration module and with a collection of more than 150 tickets resolved. It has been a massive undertaking with some great results. We also are in the documentation process and our book is available as well now:


Download ContentBox 3.0.0 RC Today!


What's New

We have created a very comprehensive what's new guide in our documentation book here:

Books, ColdBox MVC, ColdFusion, ContentBox CMS, Releases 0

CommandBox v3.1.0 Beta Ready For Testing

Brad Wood
May 05, 2016


We are excited to announce availability of CommandBox v3.1.0 Beta for testing and feedback.  Our goal is to have this released in time for Into The Box so that means we need you to help get it stable and ready to go.  There are a collection of bug fixes, and several very nice improvements, the biggest of which is the ability to start up any CFML engine you want on demand including Lucee 5, Adobe ColdFusion 2016 and Railo.

How do I get it?

First things first.  If you already have an older version of CommandBox installed, you can run this command which will give you the URL 

CommandBox> upgrade --latest

Or just hop over to our integration server and grab the correct binary for your OS:

We're still working on the GitBook docs for this release, but you can use the "help" commands to get additional info.

What do I need to know?

The first thing to take note of is that the beta of CommandBox is currently pointing to our stage server since we are using a brand new ForgeBox API.  This will be fine for testing, and even installing most packages, but it's not guaranteed to be the exact same packages as what's on production.  

If you want more juicy details on the new features of 3.1.0, please check out these two blog entries on my personal blog:

Exciting New Features In The CommandBox 3.1.0 Bleeding Edge

CommandBox Multi-Server Support Now In Beta (v3.1.0)

Also, a full list of tickets completed thus far are available here in JIRA:

JIRA Search for "Resolved" tickets in the "3.1.0" release.

What's new?

Here's an overview of the big changes and improvements in this release.  There will be more to come, but this is what we have done so far.

Multi-Server Support

The CommandBox CLI runs on Lucee Server, and the web servers you could start in any directory used to only be Lucee too.  Now you can start up a web server of any kind and version.  Currently supported CF engines are:

  • Adobe ColdFusion 2016.0.0+297996
  • Adobe ColdFusion 11.0.0+289974
  • Adobe ColdFusion 10.0.12+286680
  • Adobe ColdFusion 9.0.2+282541
  • Lucee Server (embedded, so no download needed)
  • Lucee Server 5.0.0-SNAPSHOT+243
  • Railo Server 4.2.1+008

Starting up a CF server is still super easy.  Everything you need will be downloaded the first time you start the server and cached for subsequent restarts.  

# Start the default engine
CommandBox> start

# Start the latest stable Railo engine
CommandBox> start cfengine=railo

# Start a specific engine and version
CommandBox> start cfengine=adobe@10.0.12

Start any Java WAR as a server

This goes hand-in-hand with multi-server support, but opens the door even wider to ANY Java J2EE application, which could be a custom CF engine build of your choice, or just a standard Java application.

CommandBox> server start WARPath=/path/to/explodedWAR
CommandBox> server start WARPath=/path/to/WARArchive.war

Global Server Defaults

You can store your server settings in a server.json file since version 3.0.0.  Now, we've made it even better by allowing you to provide global defaults that apply to all servers via the config settings.

CommandBox> config set
CommandBox> config set server.defaults.jvm.heapSize=1024

New ForgeBox 2.0 API

We've re-written the ForgeBox API to be better, faster, and stronger.  It supports a whole slew of new functionality to help CFML developers publish their packages and get them into the hands (and servers) of other developers.

ForgeBox 2.0 tracks multiple versions of the same package

This is self explanatory, but a huge improvement.  Your project's entire history of releases can now be tracked via ForgeBox, allowing users to install the specific version of your package that they need.

CommandBox> install coldbox@3.8.1

ForgeBox can create users from the CLI

Signing up for a new ForgeBox account just got even easier with the following command.  

CommandBox> forgebox register

ForgeBox can log you in from the CLI

You can also authenticate to ForgeBox to publish your packages and more with this new command.  You may never touch a web browser as long as you live.

CommandBox> forgebox login

ForgeBox can publish package from the CLI

Put them all together and what do you get? Only the smoothest, fastest, and most advanced workflow for managing your open source packages in the CFML space.  With one command you can shoot new packages off to ForgeBox for the entire world to see, or just update a new version of an existing package.  There's no need to log into the web site and keep stuff up to date, this command does it all for you, including reading in your readme files.

CommandBox> forgebox publish

Bumping package versions auto-tags your Git repo

In our never-ending quest to improve the developer's workflow, bumping your packages to a new version will automatically tag your local Git repo (if you're using one).  That's one less thing you need to worry about before using the publish command.

CommandBox> bump --patch message="Finalized awesome features."

Semantic Version support

Now that ForgeBox is aware of all your packages versions, the CLI is also able to use fancy version ranges to install the versions you need and allow you to update easily to new compatible versions of your packages in the future.  We've implemented full NPM-style semver support.  Check out these new syntaxes supported for packages on ForgeBox.

# Latest stable version
CommandBox> install foo

# latest version, even if pre release (bleeding edge)
CommandBox> install foo@be

# A specific version
CommandBox> install foo@1.2.3

# Any version with a major number of 4 (4.1, 4.2, 4.9, etc)
CommandBox> install foo@4.x

# Any version greater than 1.5.0
CommandBox> install foo@>1.5.0

# Any version greater than 5.2 but less than or equal to 6.3.4
CommandBox> install "foo@>5.2 <=6.3.4"

Interceptor-based CLI scripts

If you want to piggyback additional commands to run at key lifecycle events for your package, servers, or CLI, you can specify scripts in your package.json.  Scripts are commands to be run from the CommandBox interactive shell, that will execute automatically in the same working directory.  They are stored in the box.json under an object called "scripts" and keyed off the name of the interceptor you want to fire them. These are useful for additional housekeeping tasks that you want to make automatic.

  "scripts" : {
   "postVersion" : "package set location='gitUser/gitRepo#`package version`'"
   "postPublish" : "!git push",
   "onServerStart" : "echo 'Hi, thanks for starting `server show name` on port `server show web.http.port` in directory `pwd`'"

Well, don't just stand there

It's time for you to get out there and test.  Put in tickets for any bugs you find here.  To review, you can download the beta for CommandBox 3.1.0 here:

And if you want to read a more in-depth review of the features, check out these posts on my personal blog:

Exciting New Features In The CommandBox 3.1.0 Bleeding Edge

CommandBox Multi-Server Support Now In Beta (v3.1.0)



CommandBox, ForgeBox, Releases 0

ColdBox 4.2.0 Released!

Luis Majano
Apr 01, 2016


We are excited to announce the general availability of ColdBox 4.2.0. This release includes tons of fixes but also great new features and speed improvements. If you have CommandBox installed, you can upgrade now by just typing: box update coldbox or get started with a new ColdBox app by typing: box coldbox create app --installColdBox.



Here is a synopsis of the major feature updates and improvements in this release.

ColdBox MVC, Releases 0
1 2 3 4 5 6 ... 29 >>