
We are pleased to announce the 3.0.0 release of the Commandbox Docker image. This release offers a number of improvements and optimizations for runtime usage and usage in crafting custom images for deployments.
Category Selected:
commandboxCategories:
Archives:
We are pleased to announce the 3.0.0 release of the Commandbox Docker image. This release offers a number of improvements and optimizations for runtime usage and usage in crafting custom images for deployments.
We've released a very small patch release to CommandBox 5.0.0 which is 5.0.1 and has only 5 tickets. Most all are related to tweaks for the new server start bash script functionality that we've been rolling into our Ortus CommandBox Docker images.
We've been publishing all stable Lucee builds and select release candidate builds to ForgeBox for some time now. This allows you to use CommandBox CLI to start up a Lucee server running the version of your choice.
server start cfengine=lucee@5.3.4.77
Publishing these CF engines has been a manual process in the past, and was something we'd do after Lucee issued a release announcement. This has changed last week now with three major additions to our process aimed at giving you faster builds, easier testing, and more deployment options.
We are pleased to announce the release of CommandBox 5.0.0. This is a major release of our CLI package manager, REPL, and server tool. In this version are many library updates, new features, and bug fixes. All in all, there were 77 tickets closed for this release.
We are pleased to announce the first Release Candidate of CommandBox 5.0.0-RC.1 is now available. This release started as 4.9.0-alpha, but we decided to go ahead with a major version bump due to some major updates in our Java libraries. Most notably, Lucee 5.3 and Java 11 support. Please help us test this RC. If no issues are found, we'll turn it into a final release.
I wanted to highlight a recent project I help a client out with, where we used CFConfig to help automate the process of applying government STIGs to ColdFusion servers. A STIG, or Security Technical Implementation Guide, is meant to standardize the process of setting up and auditing secure servers. If you manage servers in a government or corporate setting, you may be familiar with this. If not, you should still be automating your locks downs anyway, so keep reading.
Today we are pleased to announce a minor release for our FORGEBOX suite of products to version 4.8.0. This release includes lots of fixes and some great additions for your development needs for all Editions: Community and Enterprise.
In this tutorial, Brad Wood shows how to use FusionReactor features such as the request Profiler to identify several bottlenecks of slow code in a ColdFusion app.
Today we are pleased to announce a minor release for our FORGEBOX suite of products to version 4.8.0. This release includes lots of fixes and some great additions for your development needs for all Editions: Community and Enterprise.
More and more people are using CommandBox or our Ortus Docker containers (powered by CommandBox) for production deployments. Commandbox uses JBoss Undertow which is very lightweight and fast, and capable of service traffic just as fast as IIS or Apache. A lot of people ask me about running CommandBox in production and I always say it's find so long as you follow the same basic lockdown procedures you'd take on any web server. If you have IIS or Apache sitting in front of CommandBox, most of this configuration can happen there, but for people who want drop-dead simply prod servers, here's some quick tips on locking down your CommandBox server.