I’ve been running railo for many years, and have been gritting my teeth
knowing I need to move to Lucee, but had some minor issues with updating my
test server and kept putting things off. So I decided to take a shot at
doing a complete clean install to finally begin the migration. This is a
recap of my endeavors. I’m doing this for two reasons-
- there doesn’t seem to be a “Lucee install for dummies” anywhere, and
this is an attempt to get something out in “them there internet thingies”
B) I wanted to point out some of my frustrations as to where holes are that
may frustrate n00bs that may give up before finding this info.
I created a new VM in VMWare Fusion running Centos 7, specifically
I ran a yum update to make sure things were sufficiently up to date.
Then I ran Jordan’s installer from the lucee.org site
It asked for the apache directory. That’s when I realized I didn’t have
apache installed. A simple yum install httpd took care of that. I was able
to successfully run the complete installer. Home free? Not so much.
Tried to call up the server admin page and got a 503 error. Also tried to
bring up a default cfm page. Nothing.
After an extended amount of hair pulling, I finally realized I should take
a look and see if things worked via port 8888. Voila! Able to pull up the
default lucee cfm page as well as the server admin page!
At this time I thought I would take advantage of the helpful links on the
Welcome to your Lucee Installation page. I clicked on the “First steps”
link and was taken to the bitbucket page telling me I needed to log in.
OK. Created an account, logged in, went back and got “You do not have
access to the wiki.” Now as far as I can tell, I don’t think a wiki was
ever created. I’m seeing people branching, but no wiki. I can totally
understand that if this was Lucee 5, but as Lucee 4 is what every CF
developer should be using, and has been around for a year now, even a stub
page would be an improvement.
But I still could not serve up pages via port 80. After another extensive
google hunt I
managed to FINALLY find a reference to this in a thread.
Turns out that Centos 7 minimal install automatically activates SELinux.
/usr/sbin/setsebool -P httpd_can_network_connect=1
will allow me to finally serve cfm files via port 80.
Next up, vhosts. Tried to take one of my vhost files from another server
and plop it in. Every attempt of doing an apachectl restart gave me
Job for httpd.service failed because the control process exited with error
code. See “systemctl status httpd.service” and “journalctl -xe” for details.
Tried both commands, neither gave me any details. Back to google. Turns
out that apache2 has made some very subtle changes. The most important of
which is that filenames now need to be encased in quotes, e.g.
and not as my old file had it:
I’m pleased to say that catalina worked like a charm, taking care of
setting up the tomcat web contexts for me.
I’m sure there are many other things I should be including here, but at
least this is a step by step method of creating a (fully) working BASIC
So what should I do with this? hope that this post will be sufficient to
find? Create a blog entry somewhere? Make a modified version of this the
long-lost wiki entry?
Hoping this helps someone,