The Ortus Solution roadshow continues, we'll keep bringing you free webinars and blog posts through the month of September. If you have tuned in already, you might have learned what Docker is, why you could / should use it, and then maybe a little of how to use it. If the first part of this mini series on First Docker Compose we saw how ou can spin up a Docker container pretty easily, with a command or two, but usually, we work with multiple servers. Docker-Compose makes that easier, it doesn't have to be too confusing. We are building on top of part 1, where we spun up a CFML Server container by itself, and then we added a simple MySQL Server. Next we're going to add Nginx in front of the CFML Server container, and then we'll do more with the MySQL server, like add a database, and then seed it ( preload it ) with data to get things rolling. That is what we're going to look at today.

The roadshow has just started, and you might have learned what Docker is, why you could / should use it, and then maybe a little of how to use it. You can spin up a Docker container pretty easily, with a command or two, but usually, we work with multiple servers. Configuring that might be confusing at first... you might wonder, if i spin up 3 containers, how do they know how to find each other, and other questions like this, are easily solved, with Compose files. That is what we're going to look at today.

There's a brand new thing out and it's called Docker.  Maybe you've heard of it? We think it's pretty cool. Oh, who are we kidding?  Docker has been around for a while now and it's becoming HUGE!  Local development is getting more powerful.  Server deployment is becoming more ubiquitous.  And cloud hosts everywhere are consolidating on one container standard. ...

We are excited to bring our training Bootcamp series as a pre-conference workshop for this years Adobe ColdFusion Summit 2017 in Las Vegas, NV. This training series will be led by Box creator Luis Majano and CommandBox Creator Brad Wood at the Mirage Hotel in a private training penthouse retreat. Register as soon as possible as space is very limited!

In my last post, I talked about How to hook into Hibernate ORM Events easily with CBORM and ColdBox. I talked through the what, why, how, but didn't get to the code. So this post, is going to go through the code and give you a real example you could use today to extend ContentBox's core Author module with your own function.

I have been working for Ortus Solutions for over two years now, and still, every day I learn something new about one of our modules or tools. In one of my current customer projects, we are taking a ContentBox installation ( our Modular Content Management System built on top of ColdBox ), customizing it, extending it, and it's really fun. One of the big customizations for this projects is extending the permissions structure, outside of what we wanted to do in the ContentBox core.

On the heels of and in conjunction with the 3.7.0 release of ContentBox, we are pleased to announce the 3.7.0 release of CommandBox ( a happy coincidence that the version numbers of the two are the same! ).

This release provides major updates in security and functionality to the CFConfig module, which may be used to configure CFML servers at runtime. The settings and environment variables, which were previously handled by the bash script used to start the image, are now delegated to CFConfig. You can read more on using environment variables for CFConfig here.

Today we are very excited to bring you ContentBox version 3.7.0!

Most projects in CF now involve creating some type of consumable CFC Endpoint or API Service... do you Unit test your API, do you use Integration Tests on your API? How many ways do you test your API? Not all tests are created equal.

We build our CFCs and CF API to be consumed with CF Apps, Mobile Apps, Javascript apps and devices we haven’t even thought about yet. To be smart developers we need to be able to test our CFC endpoints, and the code that uses those endpoints.

We’ve all had those projects, the salvage project, the legacy project that we picked up, and wished we never had.

Was it written 5 years ago by that young dev with lots of passion but no big picture vision.

Was it written 6 months ago by another team, by a top gun developer who knows all the design patterns, and tried to future proof the app, only succeeding in making it impossible for anyone else to understand.