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.
Recent Entries
We are pleased to announce the release of CommandBox 5.4.0. A minor update containing 30 bug fixes and enhancements that has been 3 months in the making. Our focus for this release was cleaning up some rough edges left from the 5.3.x enhancements, improvements to the CLI to support the latest modules, and enhancements to automation around environment variables.
Add Your Comment
(4)
06 Dec 2018 06:31 AM
by Mark Drew
This is great! very handy! But as it's console, where does the startup log go (in case you need to debug it's start?)
06 Dec 2018 08:21 AM
by Brad Wood
Hi Mark, the console logs still go the same place they always do. You can view them with "server log" as well as looking at the log file on disk. If you need to debug a server, I recommend just running the start command manually in a terminal to debug it. NSSM also has a logging setting you can enable that will capture ALL the output of CommandBox including any output of the "server start" command itself prior to the actual server process coming online.
13 Sep 2021 03:36 PM
by Tom
Normally when I run CommandBox, the server context resides under my user profile. When CommandBox runs as a service, does this change the server context? I need to import the password file. I'm having an issue with cfconfig at the moment (you are also helping me via FaceBook Group ColdFusion Programmers at the moment) so until I can get that resolved, I'm setting up the admin manually.
13 Sep 2021 03:56 PM
by Bradley D Wood
Tom, unless otherwise configured, CommandBox will extract itself into the user home dir. When you run it as a Windows service, it will use the home directory of the Windows System account by default (unless you configure another user for it to run as) which is buried inside your windows/system32 folder. This will give you a totally separate installation of CommandBox with different settings, modules, etc. I recommend you "pin" your server home with a "commandbox.properties" file as described in the docs here: https://commandbox.ortusbooks.com/setup/installation