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.
Once you've installed the latest 3.0.0 build, let's look around at some of the new stuff:
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.
First things first. To install the latest 3.0.0 beta version of CommandBox, download the appropriate binary for your OS here:
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.
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:
Also, the bleeding edge API docs are available here as well:
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 following Command using CommandBox:
box install docbox
The code repo and readme for DocBox is here:
We have also released our first final 1.0.0 version of the CommandBox Docbox command. If you want to generate your API docs completely from the command line without the need to even start a server, this is for you! The CommandBox commands are stored in a separate repo as well.
Install the new DocBox CommandBox Commands and use them like so:
box install commandbox-docbox box docbox generate source=/path/to/coldbox mapping=coldbox excludes=tests strategy-outputDir=/output/path strategy-projectTitle="My Docs"
Please note, these command require the latest CommandBox 3.0 beta which can be downloaded from our integration server or via the CLI as well by running the command
box upgrade --latest
This should allow you to really add some spice to your build jobs with new and easier ways to generate your API docs via Docbox.
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 read/write files.
Check out our release notes below and then head over to the download page to grab the latest box binary. It will automatically upgrade any existing installation on first run.
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 know what version they're hosting without downloading the entire package anyway.
We also included a small enhancement to the Git endpoint to allow for authentication via public/private SSH keys. As long as you have a public key configured on your Git server and the private key is stored in ~/.ssh/ using a standard name, SSH-based clones should automatically authenticate. Please see the docs for more info.
As always, the CommandBox Getting Started Guide is located here:
[COMMANDBOX-259] - update command erroring
[COMMANDBOX-263] - Git SSH endpoint private key support
[COMMANDBOX-260] - Standardize parameter names for install command
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 review of the latest features in CFML's CLI, REPL, Package Manager, and Embedded Server. We'll cover:
We will record the CommandBox Connection and make the recording available afterward. See you there!