Hi all, please be kind to the newbie who is probably about to ask very newbie questions 🙂 I was pointed in this direction by the good folks in the Facebook CF Programmers group. I have a CF2016 application which I am trying to convert to run inside a Lucee Docker container [ with the long term goal to save on Adobe license costs and deploying in an Azure container environment - it's currently running on an Azure VM ]. It is has been recommended to me that Commandbox is the way to go but, whilst I am fairly up to speed with Docker and very up to speed with CF, my knowledge of Lucee and Commandbox is not so great. I have started doing some digging with the exisiting commandbox docker images and can get a empty Lucee container running without problems. I can also build a container running Lucy and containing my application code but when I try to access the app (in the container) I get errors which are presumably caused by all my CFAdmin settings not being setup in the container. Is anyone able to point me in the direction of some sort of step-by-step guide/hand-holding to get the app running in the container ? Once I know all the settings have been included in the docker image/container then I am fairly sure I can sort out any Lucee compatibility issues. Anyone able to help ?

* sends up the @bdw429s signal *

Lol, I'm at camp for the next week with no computers!

Thanks for all that @bdw429s - all very useful. I have got commandbox running and used cfconfig to get my app's CF settings exported to a .config.json file. I think the server.json stuff is still the missing piece. Time for more reading 😀

@Adam Brunt this is a great vid to learn why one would use Commandbox Servers, plus commandbox cli basics. https://cfcasts.com/series/webinars/videos/jon-on-containerizing-cfml-applications This free video on cfcasts.com is great vid to learny why one should use containers. And you already started reading the readme in dockerhub like Brad mentioned then you'll get the full guide with this video. https://hub.docker.com/r/ortussolutions/commandbox this is the readme on dockerhub. Read everything and make sure you understand warmed-up images. Warmed up images is what you want to end up with - see the section Optimizing Startup Times. I still don't use containers in production, but I do use commandbox servers and cfconfig. environment variables, server.json and cf admin settings was the trickiest part to get right when I was beginning. Let me just say that everything is in the docs. https://cfconfig.ortusbooks.com/ and https://commandbox.ortusbooks.com/ are the docs you'll need. Ask for help and guidance in #box-products channel.

@Daniel Mejia - I definitely get the impression that your last paragraph is definitely true 🙂 I get the impression that Docker is going to be the easy part 😄 Warmed up images are where the CF/Lucee instance is already up and running, right ?

It's where the server has been started once so all the files are unpacked on disk and it will start up faster when the image deploys.

Not sure if docker part is the easiest part - I still haven't been there. Plus I think when I was beginning my mindset was stuck on how things were done for 15 years that it was hard for me to make the paradigm shift. Now I look at my server setup and think its so easy and I can't believe I wasn't doing it earlier.

is extremely useful 🙂 Got the cfcast one to go. Will take any Commandbox specfic questions to the box-products channel