Newbie Lucee Questions

dev google-group-archive
1

When I set up my Railo servers, I used Helicon Zoo, which took care stuff I
should have learned how to do on my own. Most of my work with CF has been
cleaning up really old (and really bad code) at my day job, which hasn’t
prepared me for setting up a clean instance.

While setting up Lucee, I’ve come across questions whose answers I wished
were more easily accessible.

I’ve put together what I found here and may add more stuff later in case
someone else comes here looking for information - I know that most of you
guys are way beyond this stuff, and maybe I’ll join you one day, but
hopefully there is room for guys like me for now.

My questions and the answers:

1 Setting up multiple Lucee websites on Windows/IIS:

These instructions assume you know how to set up DNS, port forwarding for
your router, and how to add a new site in IIS.

  1. Install Lucee (I installed
    http://railo.viviotech.net/downloader.cfm/id/134/file/lucee-4.5.1.000-pl0-windows-installer.exe
    from Download Lucee )
  2. Verify that Lucee is running (The internal IP of my Lucee server is
    192.168.1.80, so I went to http://192.168.1.80:8888 to view the Hello Lucee
    page, which verified a successful deployment)
  3. Set up DNS for a site, if you haven’t already (I added
    lctest.blahblah.com to my GoDaddy DNS). Set up port forwarding on your
    router, if needed.
  4. Create your local folder, if you haven’t already ( I used
    C:\sites\lctest)
  5. Add a Host entry to Server.XML - I installed to the default location
    (C:\lucee) so the path is C:\lucee\tomcat\conf\server.xml)
  6. Just above the tag, add the following Host entry:



lctest.blahblah.com

Substitute your host name and alias, and put in your local folder for
docBase

  1. Save the XML file and Restart Lucy - in Windows 2012 R2, click the Start
    button, click the down arrow, select Lucy-Tomcat Service Control
  2. On the General tab, click the Stop button. When Service Status changes
    to Stopped, click the Start button.
  3. Watch an episode of Star Trek, the Original Series to celebrate Leonard
    Nimoy
  4. Create a simple index.cfm file - if you’re stumped, you can use the
    example code from Tom Kitta’s tutorial -
    http://www.tomkitta.com/guides/cf_101.cfm
  5. Navigate to your alias - for me, it was http://]lctest.blahblah.com -
    and check that index.cfm executes

The same principles apply for migrating existing sites to a new Lucee
server, after setting up any necessary datasources and, if needed, SMTP
server.

2 Enabling Debugging on multiple Lucee websites

Create a web.config file in the site’s root folder. It should contain:

Here is a quick way to get a dump to make sure debug works:

2

I’ve put together what I found here and may add more stuff later in
case someone else comes here looking for information
it’d be great if you could add that to the Wiki, either on a new
document, or existing ones where applicable
lucee / Lucee / wiki / Home — Bitbucket

Here is a quick way to get a dump to make sure debug works:

you could do it a bit simpler by using inline struct, e.g.

Igal Sapir
Lucee Core Developer
Lucee.org http://lucee.org/On 2/28/2015 4:54 PM, Doug Roberson wrote:

When I set up my Railo servers, I used Helicon Zoo, which took care
stuff I should have learned how to do on my own. Most of my work with
CF has been cleaning up really old (and really bad code) at my day
job, which hasn’t prepared me for setting up a clean instance.

While setting up Lucee, I’ve come across questions whose answers I
wished were more easily accessible.

I’ve put together what I found here and may add more stuff later in
case someone else comes here looking for information - I know that
most of you guys are way beyond this stuff, and maybe I’ll join you
one day, but hopefully there is room for guys like me for now.

My questions and the answers:

1 Setting up multiple Lucee websites on Windows/IIS:

These instructions assume you know how to set up DNS, port forwarding
for your router, and how to add a new site in IIS.

  1. Install Lucee (I installed
    http://railo.viviotech.net/downloader.cfm/id/134/file/lucee-4.5.1.000-pl0-windows-installer.exe
    from Download Lucee )
  2. Verify that Lucee is running (The internal IP of my Lucee server is
    192.168.1.80, so I went to http://192.168.1.80:8888 to view the Hello
    Lucee page, which verified a successful deployment)
  3. Set up DNS for a site, if you haven’t already (I added
    lctest.blahblah.com to my GoDaddy DNS). Set up port forwarding on your
    router, if needed.
  4. Create your local folder, if you haven’t already ( I used
    C:\sites\lctest)
  5. Add a Host entry to Server.XML - I installed to the default
    location (C:\lucee) so the path is C:\lucee\tomcat\conf\server.xml)
  6. Just above the tag, add the following Host entry:



lctest.blahblah.com

Substitute your host name and alias, and put in your local folder for
docBase

  1. Save the XML file and Restart Lucy - in Windows 2012 R2, click the
    Start button, click the down arrow, select Lucy-Tomcat Service Control
  2. On the General tab, click the Stop button. When Service Status
    changes to Stopped, click the Start button.
  3. Watch an episode of Star Trek, the Original Series to celebrate
    Leonard Nimoy
  4. Create a simple index.cfm file - if you’re stumped, you can use
    the example code from Tom Kitta’s tutorial -
    http://www.tomkitta.com/guides/cf_101.cfm
  5. Navigate to your alias - for me, it was
    http://]lctest.blahblah.com - and check that index.cfm executes

The same principles apply for migrating existing sites to a new Lucee
server, after setting up any necessary datasources and, if needed,
SMTP server.

2 Enabling Debugging on multiple Lucee websites

Create a web.config file in the site’s root folder. It should contain:

Here is a quick way to get a dump to make sure debug works:

-- 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/c18fab4a-6621-4f4a-b7fe-6e6cf37e51bc%40googlegroups.com . For more options, visit https://groups.google.com/d/optout.
3

Done - I created this page:

https://bitbucket.org/lucee/lucee/wiki/Newbie%20Questions

And that page is now linked to on the “How to set up a Lucee Server on
Windows” page:

https://bitbucket.org/lucee/lucee/wiki/How%20to%20set%20up%20a%20Lucee%20Server%20on%20Windows

Thank you for showing me a better dump!On Saturday, February 28, 2015 at 8:16:36 PM UTC-5, Igal wrote:

I’ve put together what I found here and may add more stuff later in case
someone else comes here looking for information

it’d be great if you could add that to the Wiki, either on a new document,
or existing ones where applicable
lucee / Lucee / wiki / Home — Bitbucket

Here is a quick way to get a dump to make sure debug works:

you could do it a bit simpler by using inline struct, e.g.

Igal Sapir
Lucee Core Developer
Lucee.org http://lucee.org/
On 2/28/2015 4:54 PM, Doug Roberson wrote:

When I set up my Railo servers, I used Helicon Zoo, which took care stuff
I should have learned how to do on my own. Most of my work with CF has been
cleaning up really old (and really bad code) at my day job, which hasn’t
prepared me for setting up a clean instance.

While setting up Lucee, I’ve come across questions whose answers I
wished were more easily accessible.

I’ve put together what I found here and may add more stuff later in case
someone else comes here looking for information - I know that most of you
guys are way beyond this stuff, and maybe I’ll join you one day, but
hopefully there is room for guys like me for now.

My questions and the answers:

1 Setting up multiple Lucee websites on Windows/IIS:

These instructions assume you know how to set up DNS, port forwarding
for your router, and how to add a new site in IIS.

  1. Install Lucee (I installed
    http://railo.viviotech.net/downloader.cfm/id/134/file/lucee-4.5.1.000-pl0-windows-installer.exe
    from Download Lucee )
  2. Verify that Lucee is running (The internal IP of my Lucee server is
    192.168.1.80, so I went to http://192.168.1.80:8888 to view the Hello
    Lucee page, which verified a successful deployment)
  3. Set up DNS for a site, if you haven’t already (I added
    lctest.blahblah.com to my GoDaddy DNS). Set up port forwarding on your
    router, if needed.
  4. Create your local folder, if you haven’t already ( I used
    C:\sites\lctest)
  5. Add a Host entry to Server.XML - I installed to the default location
    (C:\lucee) so the path is C:\lucee\tomcat\conf\server.xml)
  6. Just above the tag, add the following Host entry:



lctest.blahblah.com

Substitute your host name and alias, and put in your local folder for
docBase

  1. Save the XML file and Restart Lucy - in Windows 2012 R2, click the
    Start button, click the down arrow, select Lucy-Tomcat Service Control
  2. On the General tab, click the Stop button. When Service Status changes
    to Stopped, click the Start button.
  3. Watch an episode of Star Trek, the Original Series to celebrate Leonard
    Nimoy
  4. Create a simple index.cfm file - if you’re stumped, you can use the
    example code from Tom Kitta’s tutorial -
    http://www.tomkitta.com/guides/cf_101.cfm
  5. Navigate to your alias - for me, it was http://]lctest.blahblah.com -
    and check that index.cfm executes

The same principles apply for migrating existing sites to a new Lucee
server, after setting up any necessary datasources and, if needed, SMTP
server.

2 Enabling Debugging on multiple Lucee websites

Create a web.config file in the site’s root folder. It should contain:

Here is a quick way to get a dump to make sure debug works:

-- 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 . To post to this group, send email to lu...@googlegroups.com . To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/c18fab4a-6621-4f4a-b7fe-6e6cf37e51bc%40googlegroups.com . For more options, visit https://groups.google.com/d/optout.