Goals

Create a Ruby on Rails development environment with Apache, MySQL, and PHP.

There are several possible ways of doing this, but since OS X is a Unix-based platform, I don’t see any reason to use pre-compiled packages like MacPorts and replacing the built-in software. Plus, this is supposed to be a learning experience.

Sources

http://maestric.com/doc/mac/apache_php_mysql_snow_leopard

http://michaelgracie.com/2009/09/23/plugging-mcrypt-into-php-on-mac-os-x-snow-leopard-10.6.1/

Basic Setup

OS X comes with Apache, Ruby, Rails, and PHP pre-loaded; the specific versions of each are dependent upon the installed version of OS X. In my case, I am starting with a fresh installation of Snow Leopard (10.6), and beginning by downloading all available System Updates, which brings my system to version 10.6.5, with Apache version 2.2.15, Ruby 1.8.7, Rails 2.3.5 , and PHP 5.3.3.

In order to use the pre-loaded Apache installation, go to “System Preferences” > “Sharing”  and check “Web Sharing”. This will enable the Apache web server. If you ever need to restart the server, either uncheck and re-check this box, or use the command <code>sudo apachectl restart</code> from the command line.

Next, we need a compiler, so we’ll install Apple’s Xcode Developer Tools, which can be found on the OS X installation CD/DVD and also online directly from Apple (http://developer.apple.com/technologies/tools/xcode.html). I have version 3.2.3 installed. I’m writing this up after having performed all of the updates, so the initial version may have been different.

MySQL

MySQL doesn’t come installed as part of the normal OS X distribution; just OS X Server. No problem; just download an OS X *.dmg package for MySQL Community Server: http://www.mysql.com/downloads/mysql/#downloads

Note: OS X Snow Leopard (10.6) and later compile in 64-bit C, so be sure to download the 64-bit version of MySQL (x86_64 suffix). This took me a while to figure out, as I had downloaded the 32-bit version for my 32-bit kernel. I thought it made sense. Version 5.1 should work just fine; I didn’t try 5.5.

Anyway, the MySQL *.dmg contains three files: the MySQL installer, the MySQL Startup Item installer, and the Preference Pane item. Install them in the order I have listed here. Once it’s installed, go ahead and try starting the server. The indicator in the Preference Pane item should turn green.

Edit /etc/profile and add “PATH=$PATH:/usr/local/mysql/bin”, otherwise you’ll have to type the full path to the mysql and mysqladmin executables in order to use them.

PHP

You’ll need to enable PHP by un-commenting a line beginning with “LoadModule php5_module…” in your Apache configuration file, typically found at /private/etc/apache2/apache2.conf.

Additionally, you’ll have to create a php.ini file in /etc/, which is most easily done by making a copy of “/etc/php.ini.default”. While you’re doing that, un-comment the line for your time zone, and enter a valid value. Additionally, change the three occurrences of “/var/mysql/mysql.sock” to “/tmp/mysql.sock” in order to point PHP at your MySQL installation.

I like using phpMyAdmin to manage my MySQL databases, so I’ll need to install this. The process is straightforward and well-documented. However, once you do this, you’ll notice that you’ll need PHP to have been compiled with the mcrypt extension, and the OS X distribution hasn’t been. Not to worry, Michael Gracie has a solution to that problem (http://michaelgracie.com/2009/09/23/plugging-mcrypt-into-php-on-mac-os-x-snow-leopard-10.6.1/).  Be sure to update the version numbers of the different software packages accordingly.

Restart the Apache server so these changes to php.ini take effect.

Ruby on Rails

I’m going to be using Rails 3.0, so I’ll need to update RubyGems with “sudo gem update –system” followed by “sudo gem update” to update all installed gems.

I’ll need to install a database adapter so that RoR can interface with MySQL. Rails 3 defaults to the mysql2 gem for MySQL databases, so we’ll install that with “sudo gem install mysql2 — –with-mysql-config=/usr/local/mysql/bin/mysql_config”.

I want to use the devise plugin for user authentication, so I’ll install that and its dependent gem, warden.

Finally, I want to use passenger to deploy my Rails application just to make my life easier: “sudo gem install passenger” followed by “sudo passenger-install-apache2-module” and follow the directions.

Done!

I was going to write more about configuring virtual hosts, but this post languished with “draft” status for over a week already.

Optimizing your MySQL Application

Indexing for DB performance

details: http://www.railsbrain.com/api/rails-2.0.2/doc/index.html?a=M001468&name=add_index

I don’t plan to build a giant Rails application, but Rails is known to have scalability issues. Still good to be aware of these points.

I’ve bought the eBook version of the 4th edition of the Pragmatic Programmers’ Agile Web Development with Rails. It’s still in beta, but my main goal is to see how things have changed between Rails 2.x and Rails 3. The book also covers some basic user authentication, but it’s very simplistic. In the interest of getting my project up and going quickly, I looked into authlogic and devise/warden.

Both authlogic and devise/warden were highly recommended by mischa after building an application that did some direct comparisons of several different RoR user authentication solutions. Good enough for me. devise appears to be more lightweight, so I’ll try that one first.

A little bit about my server setup: I’m hosted with Lithium Hosting, which is a great deal and has fantastic customer service. They’re not paying me to pitch the service, though clicking the link above and then signing up for a plan gives me referral credits or something. It’s a shared hosting service, so I manage my site with cPanel if I need/want to, and I’ve added on SSH access to my account so I don’t really need to use cPanel.

Once the server upgraded to Rails 3.0/Ruby 1.8.7, a couple things happened: my rails apps stopped starting automatically (cPanel feature), cPanel could no longer start my rails apps, and I couldn’t create a new Rails app with a MySQL database.

Solutions:

1) install the mysql2 gem, which is the new mysql database adapter used by Rails 3. The compilers are disabled on my host, so this was done via support ticket.

2) add mongrel to my Gemfile,

#project/Gemfile
gem 'mongrel'

Mongrel isn’t automatically started in development mode. cPanel still won’t start my application, so starting the server is done via SSH with

rails server --port=[port]

So now I can create a new project

rails new project --database=mysql

and start the server. However, I don’t have a good way of authenticating users.

So, back to the support tickets to have both authlogic and devise installed. Once tech support has done that (seven minutes. really.), check if they’re installed for me:

gem server --port=[port]

and navigate to mysite.com:[port]. They’re not, run a couple commands from the command line:

gem install devise
gem install authlogic

Which should install the gems and make them available to me. Checking again as above, and both devise and authlogic are present. Add the appropriate lines to my Gemfile. Then, since I’m trying out devise first, install it:

rails generate devise:install

That’s all for now.

I’m writing this more to file this away somewhere I won’t accidentally delete it:


class CreateLn2Locations < ActiveRecord::Migration
def self.up
# create table
create_table :ln2_locations do |t|
t.integer :vial_id
t.integer :dewar_id
t.integer :canister
t.integer :cane
t.integer :position
t.boolean :present, :default => 1
t.date :date

t.timestamps
end

# remove table
drop_table :ln2_locations
end
end


Funding at Columbia University page screenshot, 27Aug2009

The FaCU site wasn’t so much of a site as it was a page, and really, I feel I could have done a better job if I weren’t so ridiculously busy Senior year, and if I were more up to speed on using CSS to lay out websites.

Every time I’ve done this, beginning seven years ago, I’ve hit this block around how to manage the layout of a site.  The old way, working with browsers that didn’t correctly render CSS styling code, a lot of people dealt with the problem by using <table> hacks, using these tags to generate a website layout composed of “invisible boxes”.  All fine and good, except that it made changing even the smallest design element on the site was a huge undertaking, because every box was made to align and fit together like intricate pieces of a puzzle, and adjusting the thickness of one border or the geometry of one cell within the table, even by one pixel, required tweaking of every element around it, sometimes even going back and re-generating images or other graphics.

Current Garfield Messenger website screenshot, 27Aug2009

My first effort at using CSS to lay out a website was in high school, when it became my project to design and build a website for the high school newspaper.  I used it to learn not only PHP and how to interact with a MySQL database, but really everything that would be involved in developing a website.  It never became as full-featured as I wanted it to be, and it was eventually wiped out in favor of something less complex, and then again more recently for a WordPress-backed system.

Long story short, I tried to learn CSS in high school, found it supported by the various browsers available at the time in a very inconsistent manner (between browsers), and ditched it because it was too confusing to figure out how do exactly what I wanted with it.

Capstone Industries - iQueue Dispenser System

I came back to CSS during my Senior year at Columbia while I was working on not only the FaCU website, but also the website for my Senior Design Project.  I tried to adhere to only the most widely available fonts, and the lowest common resolution for both sites.  The result: fairly ugly sites, but they get the job done.

Fast forward to today, when I’m now working on moving all of the lab’s most commonly used inventory books into a user-friendly digital form.  CSS has better support across every browser, and everything just makes more sense now.  No idea why.

Still, CSS is still rendered with quite a few annoying quirks.  Take, for instance, the following page layout:

Lab inventory site

Renders just fine in Chrome, Firefox, and IE8.  The left navigation panel and the main content to the left are spaced and positioned properly.  In IE7, the main content title renders where it should, but the table appears at the bottom, under the navigation block.  In Opera, the positioning offset I used to place the content area to the right of the navigation pane doesn’t appear to be necessary, so there’s a giant gap where there shouln’t be one.

A better situation than I was working with seven years ago, but still irritating.

So far, I’ve been spending my time trying to figure out how doing all of this on a shared host will change in comparison to all the online tutorials on web development which assume that work is being done on a local machine, and with complete root user access.  I’ve done this before, but with each new host and new version of cPanel or other management software, the details change, sometimes dramatically.

Hopefully things will work out — let’s see what happens.