Installing Ruby on Rails on Snow Leopard

rubyonrails-talk
1

I'm trying to use Ruby and Rails and getting very disheartened after a day of failure with a variety of errors. I've tried various approaches from the suggestions on this and other forums, so far all without success. These include three separate ways of doing the installation.

In all cases, I've simply done the steps in the getting started guide: rails firstgo -d mysql cd firstgo rake db:create

(1) Using the built-in ruby that came with the Mac Xcode package (I believe) in /usr/bin

2

Hi,

you can try using VirtualRails : http://www.virtualrails.org

it's a free virtual linux-based Ruby on Rails development environment, all fully configured. It runs under virtualbox, and takes 5 mins to install. nonetheless you OSX won't suffer from the "rails-conf process" :slight_smile:

3

Jerome Fillioux wrote:

Hi,

you can try using VirtualRails : http://www.virtualrails. org

But you shouldn't have to. Apple's Ruby plus a working MySQL installation should be fine; search the list archives for ideas on why your setup isn't working. Better yet, switch to PostgreSQL, which is a much better database.

Best,

4

Sounds like you've done everything right, but let me throw out a stupid question: any chance your mysql server isn't actually running? When I logoff/reboot, I always forget to restart the mysql service and I get weird client errors.

Jeff purpleworkshops.com

5

Also if mysql is running, log on to mysql in the terminal using the user and password in your conf and make sure you can get in –

mysql -u [user_name] -p

6

Thanks (and the stupid questions are worth asking!) but mysql is definitely OK and running (by the way, it launches at startup - Jeff, I can point out how if you're interested).

I kind of wonder whether there's an incompatibility in the mysql password mechanism between "old passwords" and "new passwords" - the difference being in the "identified by 'mypassword'|" and the "identified by password('mypassword')" constructs. But I can't actually tell what the ruby mysql driver is trying to do...

I've given up on the mysql driver for now and am testing using sqlite3. Eventually, I may have to revisit this one.

But it's not pretty...