With the 8.0.1 update of ColdFusion, OS X 10.5 Leopard is natively supported. To install ColdFusion you simply download the 32-bit or 64-bit version of the OS X installer and walk through the installation screen. The steps I outlined below, getting a custom compiled version of the Apache 2.2.x connector are no longer necessary as CF8 ships with an appropriate connector.


I've had ColdFusion 8 running on OS X 10.5 (Leopard) and hooked to Apache 2.2.6 for a while now. However, two things have occurred that are prompting me to write this blog entry. First, I've gotten several questions on exactly how I got things working - even with the other blog entries that outline a similar process. Second, I ran into an odd issue Friday when configuring everything on my new work MacBook Pro.

This is a small part of an article I'm writing for the Fusion Authority Quarterly Update Volume 2 Issue 4, due out in February. The information is so important I felt it could not wait, and am publishing this with permission from Fusion Authority. In this blog post, I will discuss the installation issue and its resolution, and provide my consolidated, easy steps for getting ColdFusion 8 hooked to Apache 2.2.x on Leopard.

Continue Reading

Aaron West's Gravatar
About this post:

This entry was posted by Aaron West on January 14, 2008 at 8:00 AM. It was filed in the following categories: ColdFusion, Apache, Leopard. It has been viewed 26592 times and has 14 comments.

14 Responses to ColdFusion 8, Apache 2.2.x and OS X 10.5 (Leopard)

  1. Works perfectly to get the server up and running, but I've got a weird problem. When I add index.cfm to DirectoryIndex in the httpd.conf file, it doesn't seem to work. I can still access files directly, but if I leave the filename off, it downloads a .class file.

    Any ideas?

  2. That's odd. I've never run into the specific behavior you are describing. By default, index.cfm isn't served up if only a directory is requested, but after adding the template name to the DirectoryIndex directive it does. Are you running virtual hosts or anything? If so, you'll want to add the DirectoryIndex directive to any virtual host blocks as well.

  3. After a bit of Google-ing and some good old fashioned reckoning, I seem to have figured it out.

    I think the problem may be that I'm running 10.5 server on the machine. It's configured a bit differently.

    At the end of /etc/apache2/httpd.conf, there is a line that includes all files in the ./sites directory. In that directory, there is a configuration file created for each Virtual Host. Using a stock install, there is a file in the sites directory called 0000_any_80.conf (meaning accessed via any hostname/ip on port 80). Edit this file, and insert the "index.cfm" to the DirectoryIndex directive in this file.

    I think that my problem was I was adding it to a DirectoryIndex directive in the main httpd.conf file -- which was getting overridden by the included files.

    Hope that help anyone else who might be having this problem.

  4. Sorry, don't mean to multiple-comment, but I forgot one other step I took. I created a new .conf file in the sites directory called "handler.conf", and put this line in:

    AddHandler jrun-handler .cfm .cfml .cfc

  5. Glad you got it working. I figured it had something to do with your sites / virtual hosts not picking up the DirectoryIndex value from the main configuration file.

  6. Kay

    For me all works perfectly now, thanks

  7. I did not know CF could run on MAC

  8. When I try to install the 64-bit ColdFusion 8 on my Mac Pro, I get this error:

    The installer has found the following errors/warnings:
    Error: Unsupported Platform:
    This installer will only run on 64 bit mac-intel. PPC and 32 bit mac-intel are not supported. If this is a 64 bit mac-intel, make sure 64 bit JDK is the default JVM.
    Close this installer and restart installation using a 32 bit installer.

    I then went into Application/Utilities/Java/Java Preferences.app and tried both 64-bit versions of Java. I got the same error.

    Has anyone else encountered this and figured out how to install ColdFusion 8 in 64-bit mode?

  9. @Andrew - What version of OS X are you running? Just because my blog post discusses Leopard I don't want to assume you are running Leopard. ColdFusion 8 64-bit works on Leopard only. If you are running Leopard, then I must admit I've not seen your error before. Trying launching Console (/Applications/Utilities) to see if there are additional error messages.

  10. I've done some more reading and it seems the consensus is that Apple's Java Update 2 for Leopard is incompatible with the ColdFusion installer. If you installed ColdFusion before the Java update you're OK, but not the other way around.

    I'm trying this on a Mac Pro with Leopard that's less than a week old. It does have the Java update though so for now I guess I'll just run ColdFusion on a VM.

  11. @Andrew - That's great info to have. I've been running CF8 64-bit on Leopard for a while, even before it was officially supported and you had to compile your own 64-bit Apache connector.

    I would recommend you downgrade your Java version. You can either do that, or install an older version to a different location on your machine and point ColdFusion to the older version.

  12. I've been trying to figure the Java update 2 for os x and CF8 64-bit too and came to pretty much the same conclusion.

    here's the conclusion I've came to...


  13. @Ciqala Burt - Thanks for posting the comment and the link to your blog post. You have some great information on the latest Java update and how it affects ColdFusion 8. Folks, if you're having similar issues check out Ciqala's blog post and downgrade your JVM. Alternatively, you can install an older (supported) JVM in a different location and simply "point" ColdFusion to that location.

  14. no worries, I've had a bit of a personal vendetta against this problem so I've spent a fair amount of time trying to figure it out (and subsequently having to re-install my machine :( ) so it's good to finally have a pretty certain idea of what the problem was and the more people who might be affected that find out the better.

    It's all a bit rubbish though.

    As an aside if people want to hide the java update in software update I've also blogged how to stop it showing up in the update list. it's an easy thing to do but until just now i had no idea how to do it myself so others might not know either.