Get It

As usual, the only step required to upgrade is to replace your 'box' binary and the next time CommandBox runs, it will complete the install. If you used yum, apt-get or brew to install, just request the newest version.  All the binaries are also available on our download page.

If you're new to CommandBox, no worries. Just check out our installation page where we have detailed instructions for each operating system to get you up and running in about 60 seconds.

https://ortus.gitbooks.io/commandbox-documentation/content/setup/installation.html

Got It

Once you've installed the latest 3.0.0 build, let's look around at some of the new stuff:

• Config Settings - Customize and configure CommandBox just for you
• Modules - The 'Box is now modular and can be extended like never before
• Interceptors - Hook into the internals of the CLI and build upon it
• Standardized Command Packaging - Custom commands can now be packaged up as modules
• Server.json - Default every aspect of the embedded server for packaging and convenience
• Shortcut for Native OS Binaries - Mucho improved native shell executions from inside CommandBox
• Shortcut for CFML Functions via REPL - A new sweet way to run CFML functions right from the commandline
• Expressions in Command Parameters - Express yourself with new syntaxes for calling commands with dynamic inputs
• Command DSL - New features to help devs writing custom commands

There is a full write up on each of these features including examples and links to the docs here in our beta release post.  Please read through it if you want to dig in deeper to the new stuff.

http://www.ortussolutions.com/blog/commandbox-300-beta-released-for-testing

Installation

First things first.  To install the latest 3.0.0 beta version of CommandBox, download the appropriate binary for your OS here:

http://integration.stg.ortussolutions.com/artifacts/ortussolutions/commandbox/3.0.0/

The first time you run box, it will install and replace any previous installation.  If you want to go back to the previous version later, you'll need to remove the .CommandBox folder in your user home first.

Documentation

The GitBook-based docs have had major updates made to them.  Prior to the final release of CommandBox 3.0.0, you can preview the bleeding edge of our docs here: 

http://commandbox.ortusbooks.com/content/v/development/

Also, the bleeding edge API docs are available here as well:

http://integration.stg.ortussolutions.com/artifacts/ortussolutions/commandbox/be-apidocs/

We are excited to announce the general release of DocBox v2.0.5 and our new CommandBox DocBox command module.  This release brings some great features for the creation of API documents, but also the tight integration into  CommandBox to allow you to generate API Docs with only CommandBox installed.  Below you can learn more about our release.

This update fixes the installation so you can install DocBox into your project by running the...

There are a lot of people out there in the CFML world managing legacy codebases.  Some of them use frameworks that are no longer maintained, and many  use no framework at all.  A common question that I get is whether an app can be slowly converted over to  ColdBox without having to rewrite everything at once.  The answer is YES!  ColdBox will comfortably live alongside your legacy code, giving you the chance to slowly convert it over as you get the chance.  

Monday, we released CommandBox 2.2.0, the latest version of CFML's package manager, REPL, embedded server, and CLI.  We've got a nice list of bug fixes and some fancy new installation endpoints like CFLib and RIAForge.  We've bumped the underlying version of Lucee to the new stable release of Lucee 4.5.2.018 which was also released Monday. Another nice feature is that the REPL now runs in the context of the current directory meaning you can create CFCs in the working directory and r...

We have put out a patch release 2.1.1 for CommandBox today.  This fixes a bug in the "update" and "outdated" commands that caused them to error after you had installed packages from an endpoint other than ForgeBox.  Note, packages installed from HTTP(S) and Git endpoints will always show as outdated and will always update since those endpoints don't provide a way to ...

Following on the heels of our CommandBox 2.1.0 release, we will be hosting a CommandBox Connection webinar this Wednesday (Aug 19th) at 11am CDT.  Come hang out for an informal...