Sign Up for Box Training before ColdFusion Summit
CommandBox 2.1.1 Released
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 ...
CommandBox Connection this Wednesday at 11am CDT
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...
CommandBox 2.1.0 Released
We've just released a minor release of CommandBox, our CLI, REPL, Package Manager, and Embedded server. This version has a number of small fixes to CommandBox as well as the embedded libraries like Runwar. We've polished up some things like piping content and new high-res icons. &nb...
ColdBox 4 Book has arrived
We are excited to finally announce the availability of the ColdBox 4 printed and kindle book. Enjoy!
Book Release Galore!
We are so excited to announce the general availability of 5 new Ortus Books in print and kindle format about our products. We have been hard at work to produce high quality documentation and transition all our documentation to book format. We only have two more in the works right now with a target release of May (ColdBox + ContentBox). So without further ado, here are the 5 new books f...
CommandBox 1.1.1 Patch Release
We've released a very small patch release (1.1.1) for CommandBox. This is to address a small bug in the upgrade process from 1.0.0. This update affects the underlying loader libraries so you will need to download the latest binary and replace the old binary on your file system. The first time you run "box" the update will be applied.
The downloads ar...
CommandBox 1.1.0 Released
We are very excited to announce the immediate release of CommandBox version 1.1.0. This is a maintenance release that addresses much of the feedback and bug reports that we received from the community since our 1.0.0 release a few month ago. The response to CommandBox 1.0 has been phenomenal and we are excited to see so many CFML developers finding a new level of productivity. Thanks to everyone who has used CommandBox thus far and provided great feedback and ideas.
CommandBox - Mastering Parameters
CommandBox is unique from other CLIs in a couple ways. My favorite one is that everything is built around the concept of commands. Not only does this organize how CFML scripts can be run from the command line, it also greatly simplifies writing custom commands since you have a platform to build upon. Part of that platform is automatic parameter handling, which brings me to my second favorite thing about CommandBox. Many CLIs only allow for positional parameters, while CommandBox also allows for the familiar syntax of named parameters plus the convenience of flags for quick boolean controls.
Using CommandBox to manage dependencies
Dependencies are other packages that are required by another package for it to run. A simple package may have no dependencies, or it may have many. There are two types of dependencies: a regular dependency or a development dependency. Regular dependencies are ones required for operation of the main package. Development dependencies are optional and only necessary if you plan on making changes to the package you're installing. Dev dependencies would include testing frameworks or build tools.
When a package is installed, CommandBox will read its dependencies (from the box.json) and recursively install them as well. This encourages developers to write small, reusable libraries for everyone to use. When installing via a package manager, you don't have to worry about getting all the pieces installed.