Blog

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.