Do you have XCode (Mac OS X developer tools) installed? The installer is
on your OS install disk, or can be downloaded free from
www.apple.com/developer.
Also, try using SQLite, instead of jumping into MySQL. You will need to
change your database.yml file to look something like:
development:
adapter: sqlite3
database: db/development.sqlite3
and I don't recall if OS X comes with the SQLite gem installed, so do:
sudo gem install sqlite3-ruby
--
Posted via http://www.ruby-forum.com/.
I do not think I would advise using SQLite -- it's kind of underpowered
for Rails, as I understand. I would, however, suggest using PostgreSQL
instead of mySQL.
There are many websites with instructions on how to get all this
running. If you find a tutorial for Tiger or earlier, just disregard
the part about installing Ruby.
However, I'm not sure why you bothered with Rubystack. Mac OS's dev
tools include Ruby and Rails already, and the other components are easy
to install on their own. If you type 'which ruby', does that point to
Apple's Ruby or Rubystack's Ruby? Some of this might be path issues.
Best,
--
Marnen Laibow-Koser
http://www.marnen.org
mar...@marnen.org
Learn to use the quoting feature in your e-mail or forum client!
>, it points to apples ( i think ): /usr/local/bin/
> ruby
I don't think that's Apple's Ruby. Do a ls -l on that to see if it's a
aymlink and, if so, to what. If it's Apple's, it should point to
something in /Library/Frameworks. If it's Rubystack's...well...I'm not
sure. Check docs for where Rubystack installs stuff.
If I were you, I'd remove Rubystack and just use Apple's Ruby.
>
> Brad
Best,
--
Marnen Laibow-Koser
http://www.marnen.org
mar...@marnen.org
Learn to use the quoting feature in your e-mail or forum client!
>, it points to apples ( i think ): /usr/local/bin/
> ruby
I don't think that's Apple's Ruby. Do a ls -l on that to see if it's a
symlink and, if so, to what. If it's Apple's, it should point to
something in /Library/Frameworks. If it's Rubystack's...well...I'm not
sure. Check docs for where Rubystack installs stuff.
If I were you, I'd remove Rubystack and just use Apple's Ruby.
>
> Brad
Best,
--
Marnen Laibow-Koser
http://www.marnen.org
mar...@marnen.org
> I do not think I would advise using SQLite -- it's kind of underpowered
> for Rails, as I understand. I would, however, suggest using PostgreSQL
> instead of mySQL.
I'm not suggesting use SQLite for production, but for development.
SQLite is just fine, and is plenty powerful. Not to mention for someone
just getting into Rails, one less thing to deal with - setting up a
whole database server like MySql and Postgres. SQLite is built into OS
X, and as I've reminded myself, the gem is already installed in OS X.
(Many services and applications use SQLite as their backend database -
Safari, Firefox to name two)
Not if you're used to actually using relatively powerful DB features.
It may indeed be good for a beginner, however.
> Not to mention for someone
> just getting into Rails, one less thing to deal with - setting up a
> whole database server like MySql and Postgres.
Perhaps true. But that has to be done sometime, and problems may arise
with the switch in DBs.
> SQLite is built into OS
> X, and as I've reminded myself, the gem is already installed in OS X.
> (Many services and applications use SQLite as their backend database -
> Safari, Firefox to name two)
I know that -- I believe that the system CoreData routines use it, so
it's easily available. I just don't think it's well suited to Web apps.
Best,
--
Marnen Laibow-Koser
http://www.marnen.org
mar...@marnen.org
Using the default OS X Leopard setup, it should just use mongrel. Double
check that it is installed:
gem list
*** LOCAL GEMS ***
...
mongrel (1.1.5)
...