Blog

We are proud to announce the general availability of CommandBox 3.6.0!.  This is a minor release of the CLI tool that contains mostly bug fixes and small enhancements.  You can download the latest version from the CommandBox download page.  We've updated the GitBook docs and Command API docs as well.

There's a lot of command tools out there written by developers to help them automate all sorts of tasks from code refactoring, linting, and builds. Node has become a popular tool to write reusable tools that can be run from the command line, but many CF developers don't realize that CommandBox has allowed developers to [do this nativley in CFML](https://ortus.gitbooks.io/commandbox-documentation/content/developing/commands/developing_commands.html) for years now.

One of the cool things that CommandBox allows you to do is run CFML code directly from the command line via the execute command, or on Unix as a natively-executable hash bang script! This opens up all sorts of doors for scheduling cron jobs and whatnot that you can write in CFML much faster and easier than using bash or shell scripts. One common question is how to access the database from one of these scripts.

We are excited to announce an update to our quick docs API module! You can find our new UI and new API docs collections in the same address [apidocs.coldbox.org](http://apidocs.coldbox.org). However, we will be migrating them to the Ortus Solutions website in the coming weeks. The update includes lots of visual and searching improvements for any API documentation created by [DocBox](http://ortus-solutions.github.io/DocBox/), our API documentation library.

In this video Brad Wood introduces the CommandBox Host Updater Module written by Chris Schmitz:

[https://www.forgebox.io/view/commandbox-hostupdater](https://www.forgebox.io/view/commandbox-hostupdater)

which allows you to automatically add host entries to your operating system and starting servers all on port 80 for you using CommandBox. It is really a great example of a CommandBox module, but also a great tool to have for ALL your ccustom development work. Enjoy!

I had a unique use-case the other day, and I wanted to share the solution with you all.

I use [a custom `Collection` component](https://github.com/elpete/CFCollection) to handle many higher-order functions like map, reduce, filter, etc. Basically, it wraps an array or a query and lets you continue chaining these functions, kind of like [wrapping a value with lodash in Javascript](https://lodash.com/docs/4.17.4#lodash).

ColdBox modules have revolutionized the way that CFML developers can reuse and organize code.  Modules follow an HMVC, or Hierarchical MVC pattern that allows you to not only break apart your CFML app into smaller chunks, but to stack those pieces into a hierarchy that really makes sense of your code.  We also call this module inceptions-- the act of nesting modules inside of each other.  

So with that in mind, a question came across the ColdBox Google group today asking about how to access events from within nested modules and how that manifests itself in the URL.  Before I responded, I spun up a quick site in CommandBox to test and I found to my dismay that the answer was very difficult to find in our docs.  As such, I figured a quick blog post was in order since it's fairly easy to set up if you know what to do.