Skip to main content

ColdFusion 8 on Snow Leopard

I did a clean install of Snow Leopard on my Mac Pro, and although I do 100% of my work on Linux these days, many of my colleagues use Macs so I thought I'd give installing ColdFusion 8 a shot.

First problem is the CF 8 intsaller won't run without Rosetta, which is an emulation layer that allows Universal Binaries to run on Snow Leopard. (For those of you who aren't aware, Snow Leopard does not run on PowerPC-based Macs.)

I decided not to install Rosetta, so that's a non-starter. From what I understand if you have Rosetta it does work, but the JRun web server connector doesn't. This is exactly the same as it was with CF 7, when you had to get the web server connector source code and compile it using Xcode. Not a big deal, but I don't use JRun anymore and since it's more or less a dead product at this point, I really encourage people to investigate other servlet containers like Tomcat. Short answer is it's not worth my time to even worry about the web server connector.

So what to do? Since this is all Java you can use a WAR file generated on ANY machine, deploy it on Tomcat, and you're good to go. I grabbed a WAR from my Ubuntu laptop, dropped that in Tomcat's webapps directory, and it runs fine.

Just thought I'd throw that out there as another approach since in the big of Scroogling I did on the issue, it seems people are just twiddling their thumbs waiting for Adobe to release a patch for Snow Leopard.

Why wait? Scrape up another machine somewhere, fire up a VM, or beg a friend who's not running Snow Leopard to generate a WAR for you, and move to a much more flexible development environment than you get with the standard ColdFusion install.

Comments

Anonymous said…
I bet Tomcat is great, but if all you have is a CF8 standard license, you are kindda stuck with JRun...
Matthew Woodward said…
True for production, but you could certainly do this setup on development.

Popular posts from this blog

Installing and Configuring NextPVR as a Replacement for Windows Media Center

If you follow me on Google+ you'll know I had a recent rant about Windows Media Center, which after running fine for about a year suddenly decided as of January 29 it was done downloading the program guide and by extension was therefore done recording any TV shows.

I'll spare you more ranting and simply say that none of the suggestions I got (which I appreciate!) worked, and rather than spending more time figuring out why, I decided to try something different.

NextPVR is an awesome free (as in beer, not as in freedom unfortunately ...) PVR application for Windows that with a little bit of tweaking handily replaced Windows Media Center. It can even download guide data, which is apparently something WMC no longer feels like doing.

Background I wound up going down this road in a rather circuitous way. My initial goal for the weekend project was to get Raspbmc running on one of my Raspberry Pis. The latest version of XBMC has PVR functionality so I was anxious to try that out as a …

Setting Up Django On a Raspberry Pi

This past weekend I finally got a chance to set up one of my two Raspberry Pis to use as a Django server so I thought I'd share the steps I went through both to save someone else attempting to do this some time as well as get any feedback in case there are different/better ways to do any of this.

I'm running this from my house (URL forthcoming once I get the real Django app finalized and put on the Raspberry Pi) using dyndns.org. I don't cover that aspect of things in this post but I'm happy to write that up as well if people are interested.

General Comments and Assumptions

Using latest Raspbian “wheezy” distro as of 1/19/2013 (http://www.raspberrypi.org/downloads)We’lll be using Nginx (http://nginx.org) as the web server/proxy and Gunicorn (http://gunicorn.org) as the WSGI serverI used http://www.apreche.net/complete-single-server-django-stack-tutorial/ heavily as I was creating this, so many thanks to the author of that tutorial. If you’re looking for more details on …

The Definitive Guide to CouchDB Authentication and Security

With a bold title like that I suppose I should clarify a bit. I finally got frustrated enough with all the disparate and seemingly incomplete information on this topic to want to gather everything I know about this topic into a single place, both so I have it for my own reference but also in the hopes that it will help others.Since CouchDB is just an HTTP resource and can be secured at that level along the same lines as you'd secure any HTTP resource, I should also point out that I will not be covering things like putting a proxy in front of CouchDB, using SSL with CouchDB, or anything along those lines. This post is strictly limited to how authentication and security work within CouchDB itself.CouchDB security is powerful and granular but frankly it's also a bit quirky and counterintuitive. What I'm outlining here is my understanding of all of this after taking several runs at it, reading everything I could find on the Internet (yes, the whole Internet!), and a great deal…