Fresh Lucee install on a server

Hi,
I want to install a new web server.
It’s a windows 2012 R2 server, IIS is not active.
I downloaded the windows installer from the lucee.org page.

Do I have to install anything before I install lucee?
Do I need apache web server or java?

Thank you for your tipps.

Michael

I think someone mentioned the other day that the installer includes Tomcat and a JRE, but you can always download them if they are not present.

Lucee uses Tomcat/Jetty by default as the web server, so you don’t need a separate web server. You can run IIS, Apache, Nginx and maybe other web servers in front of Lucee, but it isn’t a requirement for installation.On Mar 14, 2015, at 12:15 PM, Michael Vornkahl <@Michael_Vornkahl> wrote:

Hi,
I want to install a new web server.
It’s a windows 2012 R2 server, IIS is not active.
I downloaded the windows installer from the lucee.org page.

Do I have to install anything before I install lucee?
Do I need apache web server or java?

Thank you for your tipps.

Michael


You received this message because you are subscribed to the Google Groups “Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/ff55b1c0-86a0-43a4-a9c8-81449d9a2a29%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

I did not write the following. I don’t know if the versions are the latest
in the installer. I copied it from the respective sites just as a
suggestion of what I feel could be a short helpful blurb on download page.

The Installer creates a stand-alone instance of Lucee, Tomcat, and Oracle’s
JRE specifically for use with Lucee. It can be run “by itself” or it can be
connected to a pre-installed web server: IIS on Windows and Apache on
Linux. This installer also performs the web-server to Tomcat server
connections for you, which can be customized at any point after the install
to meet your own unique needs. It uses Mod_cfml (link to details -
http://www.modcfml.org/index.cfm/documentation/) which is a
community-driven suite of programs that automatically configures Tomcat
hosts to match hosts created in Apache or IIS. Mod_cfml removes the need to
configure web sites twice - once in your web server and again in Tomcat -
and performs this task automatically for you.

If you wish to use Apache or IIS, install the web server before running the
Lucee installer.

Installer will install the following:

  • Lucee 4.5.0.42
  • JRE 1.7.0_67
  • Tomcat 7.0.56
  • mod_cfml 1.0.14

Eventually if there is a detailed installation wiki or pages on the Lucee
site add a link.

As far as I know the installer assumes that you use IIS as webserver on Windows. It will connect the two for you.

If you want to use Apache http instead of the built in tomcat webserver (coyote) you will have to connect tomcat and Apache via a connector like mod_proxy.

I think that text is too long to be included in the downloads page
itself, unless we restructure the downloads page. Having a link to docs
about it would be better I think. (As well as being sure that the
download artifacts themselves have README files too-- Adam C. can
manually keep them all in sync! j/k =])

The goal we last discussed was having the bare-minimum of downloads
available directly from the lucee.org site, and then providing links to
“community supported” bundles, so we don’t imply that lucee.org is
responsible for anything beyond the core.

A grip of these community supported bundles should start rolling out
tomorrow, fresh off the presses, for testing and comment.

I’d like to get some feedback on the ideas of, say, putting logs in one
logs directory (with sub-directories, but under one root log dir), as I
think those ideas might make maintenance easier, and we’re already doing
some customization for lucee-tomcat-modcfml-jre (<-- this bundle is the
same-ish as what the current installer installs).

One major new option is the NGINX bundle, which provides the whole
stack, as well as opening up a bag of worms about where the webroot for
the app and web server should be… currently both point at the
tomcat/webapps/ROOT/, but I’d rather use
tomcat/conf/Catalina/hostName/ROOT.xml and have a custom location (maybe
lucee/weboot)

Even better, but unrealistic I think, would be lucee/apps/[name] for the
app root and lucee/apps/[name]/web or lucee/apps/[name]/pub for the web
server root.

Although splitting the app code from the pub code may be “too much” for
folks to handle, if we at least used a custom directory for the app
host, we could standardize that location across the bundles too-- for
example, this structure:

TOMCAT:
lucee
/tomcat
/lib-lucee
/apps/defaultHost

WILDFLY:
lucee
/wildfly
/lib-lucee
/apps/defaultHost

So, say, manually upgrading the lucee libs is easy, as is switching
containers… and if we kept the server and web context config
directories under lucee/ as well, along with logs, there would be a
standard location to look for stuff, regardless of chosen flavor.

The tradeoff is that we have to configure* the various underlying
technologies (tomcat, etc.), vs. using their defaults, but we’re already
doing this for the current installer bundle.

*Not configure manually, I mean if an end-user wanted to mimic how the
installer sets up tomcat with a “vanilla” tomcat, they’d have to edit
server.xml, setenv.sh, etc. to achieve the same structure.

-DenOn 3/15/15 12:40 PM, Risto wrote:

I did not write the following. I don’t know if the versions are the
latest in the installer. I copied it from the respective sites just as a
suggestion of what I feel could be a short helpful blurb on download page.

thank you Robert,
So I first have to install Apache and then Lucee.

Greetings

Michael

The bundles that I have created are explicit about things like mod_cfml
(it’s in the bundle name, as is “jre” if it has one), tomcat, nginx,
etc, and have README files included, which we can mirror in the wiki.

Every bundle comes with a script to install that bundle as a windows
service or Linux/OS X daemon, and a script to remove it, optionally
adding/removing a user as well (except for windows, though I want to
encourage using specific users for services for every OS). (The GUI
installer just calls these scripts, which makes everything pretty
standard and easy to test.)

We need to discuss some options about standardizing setups-- for
instance I like the idea of having a root “logs” directory where lucee
and tomcat logs are kept by default (if you use the nginx bundle it
would be nice to have them there too) versus say tomcat/logs and
nginx/logs and /WEB-INF/lucee/logs | lib-lucee/lucee-server/context/logs
and it would be kind of cool to keep the web and server context configs
in something like conf/server and conf/web/someWebHash instead of with
the libs | under WEB-INF…

All of the bundles (except for the Plain-Jane war bundle) could be
configured to use these defaults, which would standardize documentation
as well. Then we wouldn’t have to say "for the WildFly bundle, look in
dir X for logs, for the Tomcat bundle, look in dir Y for logs, if you’re
using nginx, look in dir Z, etc.).

I’m kinda torn on the idea, as I like being able to say “hey, look at
that projects documentation to figure out what’s going on”, but I do
like the idea of Lucee being it’s “own thing”, vs. just something that
is running on something else (which everything is, really =]).

-DenOn 3/15/15 11:46 AM, Risto wrote:

The download page for the installer should mention requirements,
options, and what exactly is happening. Many of us know what happens and
how it works, but it might be a mystery to first timers.
For example, it doesn’t mention that it uses mod_cfml (its purpose) or
it will configure another web server in front of Tomcat for you. Doesn’t
mention if it needs JRE or not. Right now there is only a link that goes
straight to the download.

It could be as simple as a link to Lucee’s own updated version of this:

https://github.com/getrailo/railo/wiki/Installation-InstallerDocumentation


You received this message because you are subscribed to the Google
Groups “Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to lucee+unsubscribe@googlegroups.com
mailto:lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com
mailto:lucee@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/d6af1b00-193e-4103-83d6-43c7e6cbf4d8%40googlegroups.com
https://groups.google.com/d/msgid/lucee/d6af1b00-193e-4103-83d6-43c7e6cbf4d8%40googlegroups.com?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout.

The download page for the installer should mention requirements, options,
and what exactly is happening. Many of us know what happens and how it
works, but it might be a mystery to first timers.
For example, it doesn’t mention that it uses mod_cfml (its purpose) or it
will configure another web server in front of Tomcat for you. Doesn’t
mention if it needs JRE or not. Right now there is only a link that goes
straight to the download.

It could be as simple as a link to Lucee’s own updated version of this:

Actually, it could just be a few bullet points of what the installer is
capable of doing. When a more detailed installer page is available then a
link to that could be added.

Hi everyone!
I love this community :blush:.
Thank you for your help.

Michael

Have you tried copying the /opt/lucee/tomcat/webapps/ROOT/WEB-INF folder to /var/www/mysite? I have sometimes had to copy the WEB-INF folder manually to get it running.

And check permissions on /var/www/mysite, make sure Tomcat has permissions on the folders.> On Jun 23, 2015, at 4:19 AM, Bill Tindal <@Bill_Tindal> wrote:

Thanks for the help all.

I do have Lucee working on :8888 and I have Nginx working on :80

I can get Nginx to point to Lucee as long as my site files (and nginx root) are located in /opt/lucee/tomcat/webapps/ROOT

As soon as I alter the nginx root to point to say /var/www/mysite and then add a virtual host xml block in the /opt/lucee/tomcat/conf/server.xml the server becomes unresponsive.

This was a piece of cake in Railo to add virtual hosts, why does it not work in Lucee?

On Tuesday, 23 June 2015 18:19:22 UTC+10, Robert Munn wrote:
Have you verified that Lucee is running by going to http://host:8888/ http://host:8888/ (or whatever port you assigned to Tomcat/Jetty). If you can get to Lucee directly via the servlet container, your problem is with the proxy pass configuration in Nginx.

Give this code block a go. It should be inside your xml config for your site, e.g. inside a server{} block. See Nando’s blog post for more detailed info.

    # Main Lucee proxy handler
    location ~ \.(cfm|cfml|cfc|jsp|cfr)(.*)$ {
    proxy_connect_timeout       100000;
proxy_send_timeout          100000;
proxy_read_timeout          100000;
send_timeout                100000;
      proxy_pass http://127.0.0.1:8888 <http://127.0.0.1:8888/>;
      proxy_redirect off;
      proxy_set_header Host $host;
      proxy_set_header X-Forwarded-Host $host;
      proxy_set_header X-Forwarded-Server $host;
      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      proxy_set_header X-Real-IP $remote_addr;
    }

On Jun 22, 2015, at 8:10 PM, Bill Tindal <mal…@ <>gmail.com http://gmail.com/> wrote:

Anyone have some direction on setting up the following:

Ubuntu
Nginx
Lucee

I have the Ubuntu server running fine, Nginx is working however I cannot seem to get Nginx to connect to Lucee correctly. Simply times out.

If anyone has an example of the following it would be great:

nginx sites-available .conf file
lucee server.xml (example)
lucee web.xml (example)

I’ve often wondered why it is so hard for a simple installation article to be written on this when releasing software. For example:

OS > Apache > Lucee
OS > Nginx > Lucee
Various other configs like SSL…

cheers,
Bill


You received this message because you are subscribed to the Google Groups “Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+un…@ <>googlegroups.com http://googlegroups.com/.
To post to this group, send email to lu…@ <>googlegroups.com http://googlegroups.com/.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/5b25f86f-2ad4-4b37-8c6a-5201b56af36f%40googlegroups.com https://groups.google.com/d/msgid/lucee/5b25f86f-2ad4-4b37-8c6a-5201b56af36f%40googlegroups.com?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout.


You received this message because you are subscribed to the Google Groups “Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+unsubscribe@googlegroups.com mailto:lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com mailto:lucee@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/2b0820b7-a41a-4a5b-8461-e3edb8d2d062%40googlegroups.com https://groups.google.com/d/msgid/lucee/2b0820b7-a41a-4a5b-8461-e3edb8d2d062%40googlegroups.com?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout.

Anyone have some direction on setting up the following:

Ubuntu
Nginx
Lucee

I have the Ubuntu server running fine, Nginx is working however I cannot
seem to get Nginx to connect to Lucee correctly. Simply times out.

If anyone has an example of the following it would be great:

nginx sites-available .conf file
lucee server.xml (example)
lucee web.xml (example)

I’ve often wondered why it is so hard for a simple installation article to
be written on this when releasing software. For example:

OS > Apache > Lucee
OS > Nginx > Lucee
Various other configs like SSL…

cheers,
Bill

Have you verified that Lucee is running by going to http://host:8888/ http://host:8888/ (or whatever port you assigned to Tomcat/Jetty). If you can get to Lucee directly via the servlet container, your problem is with the proxy pass configuration in Nginx.

Give this code block a go. It should be inside your xml config for your site, e.g. inside a server{} block. See Nando’s blog post for more detailed info.

    # Main Lucee proxy handler
    location ~ \.(cfm|cfml|cfc|jsp|cfr)(.*)$ {
  proxy_connect_timeout       100000;
  proxy_send_timeout          100000;
  proxy_read_timeout          100000;
  send_timeout                100000;
      proxy_pass http://127.0.0.1:8888;
      proxy_redirect off;
      proxy_set_header Host $host;
      proxy_set_header X-Forwarded-Host $host;
      proxy_set_header X-Forwarded-Server $host;
      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      proxy_set_header X-Real-IP $remote_addr;
    }> On Jun 22, 2015, at 8:10 PM, Bill Tindal <@Bill_Tindal> wrote:

Anyone have some direction on setting up the following:

Ubuntu
Nginx
Lucee

I have the Ubuntu server running fine, Nginx is working however I cannot seem to get Nginx to connect to Lucee correctly. Simply times out.

If anyone has an example of the following it would be great:

nginx sites-available .conf file
lucee server.xml (example)
lucee web.xml (example)

I’ve often wondered why it is so hard for a simple installation article to be written on this when releasing software. For example:

OS > Apache > Lucee
OS > Nginx > Lucee
Various other configs like SSL…

cheers,
Bill


You received this message because you are subscribed to the Google Groups “Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+unsubscribe@googlegroups.com mailto:lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com mailto:lucee@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/5b25f86f-2ad4-4b37-8c6a-5201b56af36f%40googlegroups.com https://groups.google.com/d/msgid/lucee/5b25f86f-2ad4-4b37-8c6a-5201b56af36f%40googlegroups.com?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout.

Thanks for the help all.

I do have Lucee working on :8888 and I have Nginx working on :80

I can get Nginx to point to Lucee as long as my site files (and nginx root)
are located in /opt/lucee/tomcat/webapps/ROOT

As soon as I alter the nginx root to point to say /var/www/mysite and then
add a virtual host xml block in the /opt/lucee/tomcat/conf/server.xml the
server becomes unresponsive.

This was a piece of cake in Railo to add virtual hosts, why does it not
work in Lucee?On Tuesday, 23 June 2015 18:19:22 UTC+10, Robert Munn wrote:

Have you verified that Lucee is running by going to http://host:8888/ (or
whatever port you assigned to Tomcat/Jetty). If you can get to Lucee
directly via the servlet container, your problem is with the proxy pass
configuration in Nginx.

Give this code block a go. It should be inside your xml config for your
site, e.g. inside a server{} block. See Nando’s blog post for more detailed
info.

    # Main Lucee proxy handler
    location ~ \.(cfm|cfml|cfc|jsp|cfr)(.*)$ {
proxy_connect_timeout       100000;

proxy_send_timeout 100000;
proxy_read_timeout 100000;
send_timeout 100000;
proxy_pass http://127.0.0.1:8888;
proxy_redirect off;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Server $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Real-IP $remote_addr;
}

On Jun 22, 2015, at 8:10 PM, Bill Tindal <mal...@gmail.com <javascript:>> wrote:

Anyone have some direction on setting up the following:

Ubuntu
Nginx
Lucee

I have the Ubuntu server running fine, Nginx is working however I cannot
seem to get Nginx to connect to Lucee correctly. Simply times out.

If anyone has an example of the following it would be great:

nginx sites-available .conf file
lucee server.xml (example)
lucee web.xml (example)

I’ve often wondered why it is so hard for a simple installation article to
be written on this when releasing software. For example:

OS > Apache > Lucee
OS > Nginx > Lucee
Various other configs like SSL…

cheers,
Bill


You received this message because you are subscribed to the Google Groups
“Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to lucee+un...@googlegroups.com <javascript:>.
To post to this group, send email to lu...@googlegroups.com <javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/5b25f86f-2ad4-4b37-8c6a-5201b56af36f%40googlegroups.com
https://groups.google.com/d/msgid/lucee/5b25f86f-2ad4-4b37-8c6a-5201b56af36f%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

This might help.

http://dnando.github.io/blog/2015/01/05/advantages-of-nginx/

Got the site working finally.

However I’m still confused as to what Lucee/Tomcat is doing as it just
becomes unresponsive.

I have 1 site working fine, then add another with ONE .cfm page and it
chokes the chicken.

If I run a ‘service lucee_ctl restart’ in the midst of it churning the page
appears and this is seen in the console:

SEVERE: Could not contact localhost:8005. Tomcat may not be running.

I’ve done nothing to the LUCEE install apart from editing the server.xml to
add some hosts.

Cannot even revert to the original site that was working. Now nothing works
with Lucee just sits and spins in the browser.

All I did was add another site, why would the previous working site now
bomb ?

I’m amazed at how unstable this product is. The last version of Railo
doesn’t do this.

Looks like I’m having problems with the PID file. Anyone encountered this?
Is there a patch to install?On Sunday, 15 March 2015 06:15:31 UTC+11, Michael Vornkahl wrote:

Hi,
I want to install a new web server.
It’s a windows 2012 R2 server, IIS is not active.
I downloaded the windows installer from the lucee.org page.

Do I have to install anything before I install lucee?
Do I need apache web server or java?

Thank you for your tipps.

Michael

Just an update for everyone interested.

I switched my VPS to CentOS 6.5 x64 from Ubuntu 14.04 x64 and everything is
good (and faster). I have no idea why :slight_smile:

Used the same configurations for Nginx and Lucee.

So I would recommend not using Ubuntu 14.04 based on my experience.

An important nugget I picked up from Pete Freitag’s ubuntu-nginx-railo
repository is to use the following in the proxy configuration for nginx to
tomcat: proxy_set_header X-Tomcat-DocRoot $document_root;
I believe that it enables mod_cfml to work without any other configuration
on the nginx side.

In an earlier discussion about distros, several people recommended CentOS over Ubuntu, primarily for security and reliability. In that thread I suggested not using the 14.04 release and linked to a blog post with several factoids about 14.04 that may or may not be of concern. See this post about 14.04:

https://tim.siosm.fr/blog/2014/04/25/why-not-ubuntu-14.04-lts/ https://tim.siosm.fr/blog/2014/04/25/why-not-ubuntu-14.04-lts/> On Jun 25, 2015, at 2:52 AM, Bill Tindal <@Bill_Tindal> wrote:

Just an update for everyone interested.

I switched my VPS to CentOS 6.5 x64 from Ubuntu 14.04 x64 and everything is good (and faster). I have no idea why :slight_smile:

Used the same configurations for Nginx and Lucee.

So I would recommend not using Ubuntu 14.04 based on my experience.

An important nugget I picked up from Pete Freitag’s ubuntu-nginx-railo repository is to use the following in the proxy configuration for nginx to tomcat: proxy_set_header X-Tomcat-DocRoot $document_root;
I believe that it enables mod_cfml to work without any other configuration on the nginx side.


You received this message because you are subscribed to the Google Groups “Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+unsubscribe@googlegroups.com mailto:lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com mailto:lucee@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/c51567c1-429e-403c-955d-0f4773076845%40googlegroups.com https://groups.google.com/d/msgid/lucee/c51567c1-429e-403c-955d-0f4773076845%40googlegroups.com?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout.