We've had our CommandBox FusionReactor Module out for about 6 months now which lets you easily enable FusionReactor on your CommandBox servers. It works for Lucee and Adobe servers alike and requires no manual installation. All you need to do is install the module and add in your license key with these two commands:
CommandBox> install commandbox-fusionreactor CommandBox> fusionreactor register "XXXXX-XXXXX-XXXXX-XXXXX-XXXXX"
As more people are starting to use CommandBox to start their Adobe ColdFusion and Lucee servers, I've gotten the question of where to find their log files. The servers that CommandBox starts are full fledged servers with a web admin and all the same log files you'd expect. However, CommandBox skips the vendor installer and uses the WAR files of each engine for a quick and lightweight deployment that can be deleted later and won't conflict with other servers, no matter how many you have.
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.
This is a guest post by Eric Peterson.
I had a unique use-case the other day, and I wanted to share the solution with you all.
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.
This is our final installment of the 12 Tips of (CommandBox) Christmas and we hope you've learned some new tricks! In this last segment, we'll cover setting up custom error pages for your CommandBox-based web servers. This applies to all CF engines that you start and can help you add a bit of polish to a CommandBox-powered site you want to make public!
As we continue with our 12 Tips of (ContentBox) Christmas, we at Ortus Solutions are giving you a gift of developer productivity, we will share a few tips and tricks that will keep giving all year around. Brad Wood is also doing 12 Tips of (CommandBox) Christmas.
How do I get started with ContentBox?
Merry Christmas everyone! We hope you had special time with your family and loved ones. You may have a new year's resolution to learn something new. Well, why wait when you can learn something new right now! Today in our 12 tips of (CommandBox) Christmas, we'll do a quick crash course on semantic versioning, or semver as you'll oft see it called. You may think you know everything, but keep reading and I'll bet you learn something.