and if not journey stories, information about how ...
# lucee
g
and if not journey stories, information about how you're currently deploying and / or managing instances of Lucee, what OS / web server / lucee deployment ?
b
Hey Gareth, if you are asking because you are considering moving off ACF yourself, you are in good company. Lucee will serve you very well, but in all honesty so will BoxLang. The competition between the two has made them both a better product. Personally I develop on a Mac, and deploy to both Linux and Windows (mostly Linux). The recommended approach is to develop locally using CommandBox, then deploy to production using docker containers. I've used both Lucee images and CommandBox images, but find CommandBox images easier without the shortcomings of Tomcat. I typically use Nginx globally as a proxy server to each port running a docker container, however CommandBox itself can be configured to serve apps too. In either case, you probably don't need IIS or Apache. Hope that helps.
g
@Bill Nourse hi Bill, these questions / thoughts are my own and not of my employer. I've played around with Lucee a bit over the years but never really in a capacity for deployment, and though you might not be deploying to it, it might good practice to ensure a code base can be compiled against a different platform.
I've used Apache HTTP, IIS and Tomcat (built in web servers)
b
With docker containers, there is no concern whether your code base conflicts with the host. Each container is isolated with its own runtime and dependencies. Maybe give Docker a go to learn more. Lucee is a great product, it all comes down to why you would use it... Lower cost is certainly one reason. Cheers.
e
not exactly sure what you are asking, Gareth. If you are asking, have some of us moved off AFC for Lucee? Absolutely. We have a really old application written back when Macromedia was a thing, In AFC we could not keep using some removed features from Coldfusion. In Lucee and, previously, Ralio, we were able to get the custom code working as we could directly see how the jars interacted with the underlying engine and backport the functionality to keep the code working. -- In migration to Lucee, there has been only a few minor gotchas. Some custom-compiled files do not work, some Windows-only features you will not find in Lucee, such as CFPRINT, but some workarounds actually work better. It's not as painful as you may believe, but you are trading the loving embrace of support techs to public forms and the grumpy guy at the end of a bar trying to chow down breakfast at a bar to answer this question. 🙂
a
We deploy IRO 300 website instances all on Docker containers have Undertow ( same as commandbox) + Nginx. Our Journey was ACF --> Bluedragon -- >Railo --> Lucee.