Lucee, new fork of Railo, has launched

This post is more than 2 years old.

This is definitely not new news, but I wanted to share it with folks who may have missed the myriad other posts as well. As the title says, Lucee was launched as a fork of the Railo project. I haven't used Railo much (typically only when a client requires it), so I don't follow that "world" much, but if you want to know more about the why of it I encourage you to read Adam's announcement post where he has a FAQ about the launch of the whole thing.


You can find out more, and download the bits, at the main site:

I played with it for a grand total of 10 minutes, just to see how well it works. You can currently download an "Express" edition that allows for unzip and run. If you are like me and a bit unfamiliar with how Railo did things, here are some tips:

First, the port that Lucee will run on is 8888. I'm sure this is documented in some XML file some place but it took me a few minutes to find it. I already logged an ER with them to make the startup script actually say this when it runs.

Second, you can find docs at localhost:8888/lucee/doc/.

If you want to write CFMs and test them, go to the installation folder, then webapps/ROOT. This works just like Adobe ColdFusion - write a CFM, save it, open it in your browser.

So that all involves running it locally, how about finding out more about the project?

As I said above, the main site is:

The forum for Lucee may be found here:

The source (and bug tracker) for Lucee may be found here:

The wiki for Lucee may be found here:

All in all, an interesting development. Any of my readers playing around with this yet?

Raymond Camden's Picture

About Raymond Camden

Raymond is a senior developer evangelist for Adobe. He focuses on document services, JavaScript, and enterprise cat demos. If you like this article, please consider visiting my Amazon Wishlist or donating via PayPal to show your support. You can even buy me a coffee!

Lafayette, LA

Archived Comments

Comment 1 by Dan Kraus posted on 2/1/2015 at 3:50 PM

Oh yeah, we're rebuilding our dev VMs with Lucee and Ansible for provisioning. This couldn't have happened at a better time for my team as we're about to start a major application.

I love the direction the Lucee project looks to be headed, more aggressive about doing things the sane way, and not just "me-too" with Adobe. I like that it's being positioned as scripting language on the JVM that is compatible with CFML.

Comment 2 by Gavin Pickin posted on 2/1/2015 at 4:41 PM

I have a few blog posts lined up for it already... Documenting getting it running and customizing ports, include files etc.

Already submitted some ui fixes to admin.
Always fun to play with the new and shiny stuff.

Comment 3 by Sean Corfield posted on 2/1/2015 at 11:08 PM

Yup, already in the process of migrating from Railo to Lucee. Migration is easy and it looks solid so far.

Comment 4 by jimcumming posted on 2/2/2015 at 10:52 AM

Hi Ray. The Lucee forum has moved over to a Google Group

Comment 5 by Liam Clark posted on 8/28/2015 at 7:56 PM

Can someone explain to me in short what is the difference between lucee and railo?
Also, i have Centos 6 on my server. Can I follow this tutorial?

Thanks for the help.

Comment 6 (In reply to #5) by Sean Corfield posted on 8/28/2015 at 8:03 PM

Short version: Think of Lucee as "the next version of Railo".

Longer version: The last published version of Railo was 4.2. Lucee built on that code to create Lucee 4.5, and is currently planning Lucee 5.0. Railo has no developers and is unlikely to produce any new versions (the developers left Railo to go and build Lucee). There are two security exploits in the wild that affect Railo, which are both fixed in the latest Lucee version. One is a remote code execution exploit and is therefore serious. The other is an exploit for the admin, less serious, but I'd still want both patched -- and that's why my company switched from Railo to Lucee.

Does that help?

I have no idea about the tutorial but you should join the Lucee mailing list and ask for help there. Or join the CFML Slack and ask in the #lucee channel: http://cfml-slack.herokuapp...

Comment 7 (In reply to #6) by Liam Clark posted on 8/28/2015 at 8:16 PM

Thank you very much Sean. This clears things up a bit. :)
Have a lovely rest of the day.

Comment 8 (In reply to #6) by Raymond Camden posted on 8/29/2015 at 12:07 AM

Thanks Sean - you answered it far better than I could have.

Comment 9 (In reply to #6) by YIRMASTER posted on 4/27/2016 at 12:09 AM

That isn't what the majority share holder of Railo said. Apparently this will be fought out in court in the UK.

Comment 10 (In reply to #9) by Sean Corfield posted on 4/27/2016 at 12:19 AM

According to the Lucee Association Switzerland folks, absolutely no action has been taken by what's left of Railo, because they have no legal case -- and the Lucee project has continued to forge ahead.

The "majority shareholder's" view appears not to have been shared by the other shareholders in Railo and well over a year has passed since the Lucee fork was announced, and nearly a year since that bit of saber-rattling was published on the Railo blog.

Not sure why you felt compelled to link to that post from so long ago?

Comment 11 (In reply to #10) by YIRMASTER posted on 4/27/2016 at 1:31 AM

Because you posted an explanation what Lucee was explained telling people they should switch because Lucee was more secure better option however Railo website has something else to say and litigation can take a while to settle, not sure how or what info you'd have about their litigation unless you are part of Lucee or Railo, I'm not so wouldn't know, just posting the only information from either side on that matter.

It would be important for people to know and be aware of possible legal issues that could potentially effect their project.

Not sure why you seem mad about me posting that info.

Comment 12 (In reply to #11) by Raymond Camden posted on 4/27/2016 at 1:32 AM

Heh, if you think that's Sean mad - you may be a bit sensitive. ;)

Comment 13 (In reply to #11) by Sean Corfield posted on 4/27/2016 at 1:36 AM

I replied like that because you don't seem to have done any research on the current state of play vis-a-vis Lucee and Railo -- so your post simply comes off as spreading Fear, Uncertainty, and Doubt. And that needs to be challenged.

Comment 14 (In reply to #12) by YIRMASTER posted on 4/27/2016 at 3:17 AM

Don't know him, mad may have been a bad adjective, snippy would be better.

Comment 15 (In reply to #14) by Sean Corfield posted on 4/27/2016 at 4:05 AM

I'll take snippy. :)

Comment 16 (In reply to #10) by Adam Cameron posted on 4/27/2016 at 7:39 AM

Yeah, they did the same thing on my blog too. Seems like a lot of effort to go to to share stale news with people who already know about it, and have discussed it to death.