Im trying to install rails gem on OSX 10.5.6, but when i use the gem
install rails command this message displays WARNING: Installing to
~/.gem since /usr/local/lib/ruby/gems/1.8 and
/usr/local/bin aren't both writable.
Successfully installed rails-2.3.2
1 gem installed
How can I get my gems to install to /usr/local/lib/ruby/gems/1.8 or
/usr/local/bin which both are set up in my environment variable path.
Also When trying to start my server for my rails project using
./script/server its displaying
Salafee:views_demo musdev$ ./script/server
=> Booting Mongrel
=> Rails 2.3.2 application starting on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server
Then when I go to http:/localhost:3000, and click on About your
application environment I see a message saying
Welcome aboard
You’re riding Ruby on Rails!
About your application’s environment
We're sorry, but something went wrong.
We've been notified about this issue and we'll take a look at it
shortly.
Im trying to install rails gem on OSX 10.5.6, but when i use the gem
install rails command this message displays WARNING: Installing to
~/.gem since /usr/local/lib/ruby/gems/1.8 and
/usr/local/bin aren't both writable.
Successfully installed rails-2.3.2
1 gem installed
How can I get my gems to install to /usr/local/lib/ruby/gems/1.8 or
/usr/local/bin which both are set up in my environment variable path.
sudo gem install ....
That will prompt you for your administrator password. It might also install it into /Library/Ruby/Gems (which should be in your ruby load path as well by ddefault).
Also When trying to start my server for my rails project using
./script/server its displaying
Salafee:views_demo musdev$ ./script/server
=> Booting Mongrel
=> Rails 2.3.2 application starting on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server
Then when I go to http:/localhost:3000, and click on About your
application environment I see a message saying
Welcome aboard
You’re riding Ruby on Rails!
About your application’s environment
We're sorry, but something went wrong.
Open up log/development.log and see what it says.
That initial page loads because public/index.html exists so mongrel isn't even touching rails at that point.