Modernize all things!

FORGEBOX v5.4.0 released!

See Plans

We are so excited to bring you a minor but huuuge release for FORGEBOX and all of its editions. Here are the major updates for this release and the full release notes.

Major Updates

ColdBox 6

We have made the upgrade and forgebox.io is now fully powered by ColdBox 6.1.0. This was a major upgrade to our entire framework engine and we are reaping the so many benefits of the ColdBox release. From async operations, to major rendering improvements. The entire logging enhancements on its own have rendered a 2x performance boost for API calls. We have also analyzed our traffic data and our page rendering has increased by 27% due to the ColdBox 6 Rendering capabilities. These are significant boosts in performance and stability just by the underlying framework on itself. Great job ColdBox Team!

Modernize all things!

FORGEBOX v5.1.0 released!

See Plans

Today we are pleased to announce a minor release for our FORGEBOX suite of products to version 5.1.0. It has tons of updates and nice features for all plans. Enjoy!

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.

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.

Today we are pleased to announce a minor release for our FORGEBOX suite of products: version 4.5.0. This release includes lots of fixes and some great additions. Keep reading for an in-depth review of the release.

# FORGEBOX v4.x Has Landed We are so excited to bring one of the biggest releases for FORGEBOX in over a year. We have been working and learning from all the community feedback and have major news to share with the ColdFusion (CFML) world. The full release notes of this major version can be found at the end of the blog post, so read on for all the details of this release. Below we will discuss the major areas of improvement for FORGEBOX ## New UI

The entire UI has been redesigned and updated and we are not even done yet. More is coming for the entire UI/UX experience of FORGEBOX including the CommandBox integrations.

We love Digital Ocean for many reasons, that list of reasons includes a big one - Digital Ocean is powering our Production Infrastructure.

For a long time, Digital Ocean has been a great way to get affordable, powerful and simplified Cloud computing up and running. For as little as $5 per month you can get a nice little droplet ( VM ) up and running in seconds, to host your ColdFusion app, wordpress site ( excuse my language ) or even Docker instances or a full Docker Swarm. Digital Ocean keeps improving its offering, and this year, we committed to moving our production infrastructure over to Digital Ocean, and now I'm happy to say we've been running on Digital Ocean for months now, and things have never been better. We get a lot of questions about how our setup looks, so this post will give you a little more insight into our Production Infrastructure, powered by Digital Ocean.

ForgeBox 3.0.0 has landed with tons of new features and updates including ForgeBox Storage and ForgeBox Lucee Provider!

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.