Blog

Hi everyone, great news! Ortus is rolling out our new Ortus Community site to help consolidate all of our community support and interaction. As part of that effort, all our Google Group threads have been imported to the new Ortus Community and effective immediately, our Google Groups are closed for further posting.

Yes, that’s not a typo, we really mean it: FREE forever! ContentBox, our modular content management engine that allows you to easily build websites, blogs, wikis, complex web applications, and RESTFul web services, will always, and we repeat, always be Open Source and FREE. You can use all of its goodies and features when you want them and wherever you want them.

Being a new platform from Ortus, I wanted to take some time to dive in to the tech stack we are using to build CFCasts. Many people ask us how we would build a modern CFML site. Well, here's at least one answer.

We are pleased to announce a major release of the official ContentBox Docker image. It now ships with the latest CommandBox image as well and sports a much more detailed versioning strategy:

{variant}{contentbox_version}_{image_version}

This will allow you to visualize that each ContentBox version can be paired with new image versions. This will also allow for rollbacks and rolling upgrades if necessary; all following semantic versioning. So let's dig in to this release!

At Ortus Solutions we are known for building open source projects for the ColdFusion (CFML) community such as ColdBox, CommandBox, ContentBox Modular CMS, ForgeBox and many more. All of those products are licensed under the Apache 2 license and are completely FREE to use and extend.

Today we are very excited to bring you the release of our latest Docker container for ContentBox v4.2.1. This is a major re-work of our container images as we now support over 5 different variations of our images, from warmed up servers to alpine versions of ContentBox. We have also added tons of new optimizations and environment variables to control container deployments. Ultimately, we have also updated our images to leverage the latest CommandBox 4.5.0 image!

Learn more about ContentBox at https://www.ortussolutions.com/products/contentbox and more about Docker deployment here: https://contentbox.ortusbooks.com/getting-started/installation/docker

Release Notes

v4.0.0

• Disabled directory browsing for security
• Added docker hostname to Application name in Application.cfc
• Added a rolling file appender for all app logs to go to > /var/log/contentbox.log
• Upgrade to latest CommandBox v4.5.0
• Updated healthchecks to permit load up times and consistency
• No runtime flags where ever being used, revamped it to warmup the server correctly and leverage environment variables for execution
• Removed support for lucee 4.5
• BE env variable was never working so you can test bleeding edge versions of ContentBox

Today we are very excited to bring you the release of ContentBox v4.2.0. This is a minor release of ContentBox and it sports tons of new updates, improvements and bug fixes including a major upgrade to ColdBox v5.3 which in itself gives us tons of new updates and features.

Here are the what's new guides for our release:

• What's new with v4.2.0
• What's new with v4.1.0
• What's new with v4.0.0

Today we are very excited to bring you the release of our latest Docker container for ContentBox v4.1.0. This is a major re-work of our container images as we now support over 6 different variations of our images, from warmed up servers to alpine versions of ContentBox. We have also added tons of new optimizations and environment variables to control container deployments. Ultimately, we have also updated our images to leverage the latest CommandBox 4.2.0 image!

Learn more about ContentBox at https://www.ortussolutions.com/products/contentbox and more about Docker deployment here: https://contentbox.ortusbooks.com/getting-started/installation/docker

Today we are very excited to bring you the release of ContentBox v4.1.0. This is a major release of ContentBox and it sports tons of new updates, improvements and bug fixes including a major upgrade to ColdBox v5.x which in itself gives us tons of new updates and features.

Here are the what's new guides for our release:

• What's new with v4.1.0
• What's new with v4.0.0

CommandBox is a great product, and it is always improving. Recently, one of those improvements threw a MASSIVE wrench in my world, and it might affect you too. Long story short, ContentBox stores custom modules, themes, widgets inside of the ContentBox module, usually with some tricky gitignore magic, you can ignore the core, and just commit your custom code to your repo. Now, after an update to CommandBox, if you do a install contentbox --force to update ContentBox around your changes, you might be surprised when CommandBox deletes all of your ContentBox modules, all of your ContentBox themes, all of your ContentBox widgets. Why CommandBox hates us all of a sudden?