Learn about Task Runner improvements in CommandBox 4.0 CLI for CFML and ColdFusion

Learn about using 256 color support and the CommandBox Bullet Train module in this new screencast.

We've made another screencast for you and this one shows how you can run CommandBox sites behind an IIS web server using the Boncode connector.  If you're interested in using CommandBox for easy management of your production websites, this allows static files like images, JavaScript, or PDFs to be served by the web server.  It can also be handy if your site requires some IIS-specific features but you still want the portability and ease of deployment that comes with CommandBox and CFConfig.  

A common question we get now is how to take a CommandBox server and wrap it in a Windows service so it starts automatically at boot time.  This is ideal for production use or just a dev site that you always want to stay running.  With this new screencast, you will learn how to take any CommandBox server and install it as a Windows service using a free tool called NSSM.

The package link and package unlink commands are fairly new to CommandBox and here's a brief screencast that shows you a real life use case for them.  The package link command will create a symlink from your current directory into your CommandBox's system modules folder and reload your shell. 

We've made a new screencast that shows an introduction to FusionReactor Cloud, a new way to monitor any number of servers in a consolidated interface that can scale up and down with your infrastructure.  Not only do new servers automatically register and deregister themselves with the Cloud dashboard, but it supports a pay-for-what-you-use model that prevents you from locking into a specific number of licenses.  

The roadshow has just started, and you might have learned what Docker is, why you could / should use it, and then maybe a little of how to use it. You can spin up a Docker container pretty easily, with a command or two, but usually, we work with multiple servers. Configuring that might be confusing at first... you might wonder, if i spin up 3 containers, how do they know how to find each other, and other questions like this, are easily solved, with Compose files. That is what we're going to look at today.

We've been using our CommandBox Docker images for awhile now for multi-tier development and deployment. We've also received a lot of great feedback from the community that has helped to expand the power and flexibility of the those images in orchestrating CFML server environments.

One important aspect of non-development deployments of applications on the CommandBox image, is the need to warm up the server by seeding the CFML engine file system and configuration before the application is deployed in its target environment/tier. Other than the default Lucee 4.5 engine, which is what CommandBox, itself, runs on, any CFML engine specified in your application's server.json file is downloaded upon server start. Depending on the latency of your Docker environment's connection, this can mean that a bare-bones first run of your application can take minutes to start up, rather than seconds. For obvious reasons, this is not desirable.

Don't know what a container is? Continue down and we will show you what it's all about!

Using "testbox watch" to Automate Your Testing Suite

CommandBox> upgrade --latest