Deploying ColdFusion on OS X using Parallels - Disadvantages

As I wrote yesterday in Deploying ColdFusion on OS X, there are quite a few advantages in using Parallel's virtual mahine technology to deploy ColdFusion on an Intel Mac running OS X.

But to be fair about it, there's a couple of disadvantages to doing so as well. Let's cover those quickly so we can get to the "how to".

They are...

1. Working in Windows
   
2. Security
   
3. Cost
   

The first item on the list is working in Windows. A good portion of your test server configuration is going to be done in Windows and in IIS, something that may make a die-hard Mac user cringe, duck, and cover.

But as I indicated yesterday, if your production servers are also Windows-based, this means that you probably already know how to manage a Windows box and that you can transfer IIS and CF settings and mappings wholesale to your VM environment. So in my mind that's a wash.

Next up is security and the 140,000 known viruses ready to eat your Windows machine alive.

Don't worry. You're safe. Parallels ships with Kaspersky's AntiVirus system, Windows firewall works pretty well, and your Windows VM is hidden away behind a Parallels NAT screen.

It's also easy to backup a Parallels VM and virtual HD, so if one ever does get infected, just zap it and copy over a backup. (Also handy if you completely screw up a software installation.) Compare that to doing a Windows reinstallation on a actual HW box.

So now we're down to cost: You're going to need a copy of Parallels, a copy of Windows, and your computer may need some more RAM. Let's tackle each one.

First, Parallels Desktop for Mac is available from Amazon for $65.00, a savings of $14 over retail.

Second, Windows. If you have a non-OEM version of Windows you can install or transfer, great. Otherwise, if you need to buy one, go to Amazon and get the Microsoft Windows XP Professional SP2B for System Builders version and save yourself $90 over the standard consumer version. You're going to need XP Pro and not Home for the networking setup and to get IIS and FTP and all of that other fun stuff going.

Third, memory. While Parallels/Windows with a 512MB partition worked reasonably well on my 2GB 17" MacBook Pro (my main development and "travel" machine), upgrading to 3GB made a huge difference in performance and system responsiveness. Well worth doing even if you're not running Parallels.

You can get a 2GB ram assembly for your MacBook Pro at Other World Computing. (They're also selling 250GB notebook drives, if you're interested.)

So, best case is $65. If you need Windows add $179. Considering I just spent $1,300 on an Adobe Creative Suite upgrade, a couple of hundred bucks is a no-brainer.

Another way to rationalize the cost is the fact that I have five current copies of my "base" VM installation. One for myself, three for my current client's projects, each with a different CF/IIS/SQL configuration, and now one that has CF8 installed so I can play with it as well.

I'll probably clone one of my customers VM's and upgrade it to CF8 for testing, as they've expressed interest in upgrading as soon as CF8 is released and stable. (Oops. Lost count. I just remembered I have another one with Blue Dragon installed.)

So how much would seven Windows test boxes cost me? How easily could I clone a server's HD to test CF8, while keeping a server with CF7 for current testing and maintenance? How easily can I back them all up and restore them? How easily can I zap one once I'm finished with it?

To my mind, having all of these "virtual servers" immediately available is the key aspect to consider. If you're just doing a little testing and playing with CF, then Parallels may not be for you. Install the native OS X version.

But if you're a developer or consultant, and especially if you're one with multiple clients, then the Parallels VM solution is a no-brainer.

* * *
Next: Deploying ColdFusion on OS X using Parallels - Linux
Instructions: Deploying ColdFusion on OS X using Parallels - Installation

Comments

[Rob Wilkerson]

I realize that your articles focused on Windows, but using Linux as your VM OS will negate(or go a long way towards negating) all of these disadvantages.

Either way, for me, any disadvantages pale when compared to the ability to keep my Mac running clean while still having easy access to my development environments and having the ability to develop on any number of development configurations quickly.

[Michael Long]

It's true that you can use Linux as well, but some of the key benefits of using Windows lie in having access to SQL Server and Internet Explorer.

That said, I do have an Ubuntu distro installed as well (grin).