Snow Leopard is out and I like having the latest and greatest, so I bought a new hard drive and clean installed Snow Leopard on it. This meant that I had the opportunity to reinstall my development environment with the benefit of a few years of experience and the advice of my fellow TWG’ers.
Here’s how I got my newly installed Snow Leopard up to speed for Rails development.
First, I got Ruby up to date. Snow Leopard comes with Ruby 1.8.7 by default. There are many benefits to going with Ruby 1.9.1, so I went with that.
I wasn’t 100% ready to commit to Ruby 1.9.1, so I used rvm to manage my Ruby interpreters. Many gems aren’t ready for 1.9 prime-time, so I wanted the ability to drop back to Ruby 1.8 if this blew up in my face. For an overview of what is working under Ruby 1.9, check out isitruby19.com.
I installed rvm with:
[ccN_bash”]sudo gem install rvm
Check out the rvm site for more information. There’s some great documentation there.
Next, I ran
to see all my installed Ruby interpreters. When you do this, you’ll see that the only Ruby installed is the system Ruby 1.8.7.
I ran [cciN_bash]ruby -v[/cciN_bash] to see which Ruby was being used by default. I saw that I was using Ruby 1.8.7:
[ccN_bash]ruby 1.8.7 (2008-08-11 patchlevel 72) [universal-darwin10.0][/ccN_bash]
[cciN_bash]rvm[/cciN_bash] will happily install and activate any version of Ruby you want.
I got it to install Ruby 1.9.1 with the following:
[ccN_bash]rvm use ruby -v 1.9.1[/ccN_bash]
rvm will check to see if 1.9.1 is installed and, if it isn’t, it will download and install it for you. Once that is done, I ran [cciN_bash]rvm list[/cciN_bash] again and now saw Ruby 1.9.1 listed as well as Snow Leopard system Ruby.
After that was complete, I ran [cciN_bash]rvm 1.9.1[/cciN_bash], and then [cciN_bash]ruby -v[/cciN_bash] and saw that it worked:
[ccN_bash]ruby 1.9.1p243 (2009-07-16 revision 24175) [i386-darwin10.0.0][/ccN_bash]
But, I wanted Ruby 1.9.1 to be the default on my system. I got rvm to set that default by executing:
[ccN_bash]rvm 1.9.1 –default[/ccN_bash]
Now, the system is set to use Ruby 1.9.1 by default.
Side note: one of the neat features of rvm is that it can change your Ruby interpreter on-the-fly for you. This change isn’t permanent and only lasts for as long your Terminal session is open. For example, you can open one Terminal, execute ‘rvm system’, and have that Terminal use the Snow Leopard Ruby 1.8.7 while another one is running Ruby 1.9.1. This is very handy for compatibility testing.
The next piece of the puzzle was MySQL. I have found that the best way to install packages like MySQL is via MacPorts.
If you haven’t done it yet, install MacPorts from here. There’s a package for Snow Leopard, so be sure to select that one.
The MacPorts MySQL package is called [cciN_bash]mysql5-server-devel[/cciN_bash], so I installed that:
[ccN_bash]sudo port install mysql5-server-devel[/ccN_bash]
MacPorts will handle all the dependencies and then install MySQL. I followed all the post-install steps that the installer recommended – start-up items, etc. The MySQL it installed is 64-bit, as it should be.
I then had to connect Ruby with MySQL and I needed the gem for that. To properly install the gem, I had to specify the architecture and the location of the mysql_config5 utility. The arch setting ensured that I got a 64-bit gem to go along with my new 64-bit MySQL installation.
[ccN_bash]env ARCHFLAGS=”-arch x86_64″ sudo gem install mysql — –with-mysql-config=/opt/local/bin/mysql_config5[/ccN_bash]
I then ran [cciN_bash]gem list[/cciN_bash] to see what gems I had installed. If you do this, you’ll see what I saw: not much. This makes a lot of sense because gems are installed relative to the version of Ruby they were installed with. So, all the gems that Snow Leopard had installed for Ruby 1.8.7 are no longer around for use. It was at this point that I was happy I used [cciN_bash]rvm[/cciN_bash]. I dropped back to 1.8.7, got the list of installed gems and proceeded to re-install them under Ruby 1.9. But, dear reader, you don’t need to do this! Here’s how to get back to the default Snow Leopard gems under Ruby 1.9:
[ccN_bash]sudo gem install actionmailer actionpack actionwebservice activerecord activeresource activesupport acts_as_ferret builder capistrano cgi_multipart_eof_fix chronic daemons dnssd fastthread gem_plugin haml highline hoe hpricot javan-whenever libxml-ruby mdalessio-dryopteris needle net-scp net-sftp net-ssh net-ssh-gateway nokogiri pauldix-feedzirra pauldix-sax-machine rack rails rake RedCloth ruby-openid ruby-yadis rubyforge rubygems-update rubynode rvm taf-curb[/ccN_bash]
This’ll take a while. Go grab a coffee. Run around the block. Do something fun.
If any of these fail for you, check out isitruby19.com for tips on how to get it working.
The next piece I needed was Passenger aka mod_rails. I needed version 2.2.5 (newest as of writing) for this to all work together. I installed it with:
[ccN_bash]sudo gem install passenger[/ccN_bash]
This retrieved and compiled Passenger 2.2.5 for me. It might get a newer version for you. Once that completed, I ran:
The Passenger module depends on your current Ruby version, so you have to re-compile Passenger if you change your Ruby version. It is important that the Passenger compilation properly links with the Ruby interpreter you want to use. In this case, that’s Ruby 1.9.1.
When you do this the Passenger installation, double-check the paths that the Passenger compilation process outputs and ensure that it is properly finding the Ruby 1.9.1 installed in your .rvm directory. If you see paths that don’t go to .rvm in your home directory, then it is doing it wrong. If this happens, ensure that rvm is set to use 1.9.1 by default and try again.
Next, I edited my httpd.conf just as the Passenger installer recommended. I opened it up with [cciN_bash]open /etc/apache2/httpd.conf[/cciN_bash] and pasted in the Passenger lines.
The Passenger Preference Pane makes everything easier, so definitely wanted that.
I got lucky and found that it had just been updated to support Snow Leopard, so make sure you get version 1.3 or greater.
Set up a Rails project in the Passenger Preference Pane and try it out! You should see your fully functional Rails app running.