Women in Technology

Article:		Rolling with Ruby on Rails
Subject:		Installing Rails
Date:		2005-01-25 05:48:44
From:		APC
This Ruby Gems thing looks very good in theory but doesn't work for me as it keeps timing out (errno:ETIMEDOUT). I assume this is because there is something about the --remote process that my company's firewall doesn't like. I have manually downloaded the Rails.zip but the install process still fails - it can't find a local copy of a rails*.gem file, so it starts up a remote process, which times out. I have googled for installing Rails manually but everything just seems to say, "use Gems, it's that easy!" Well, I guess when it works, it's that easy. This experience makes me dubious about the whole premise. The apparent benefit of Ruby is that it makes everything easy. So easy that there is apparently no need to document a harder way of doing the same thing. But, when that easy way doesn't work we're left stitched up like a kipper. Stupendous productivity savings in development times is no good if they are frittered away trying to install stuff. Cheers, APC

Showing messages 1 through 6 of 6.

• Installing Rails
  2005-01-25 06:32:57  Curt Hibbs | [View]
  
  
  I think that you are experiencing the tsunami effect of slashdot: the RubyForge servers have been hammerred ever since this article was mentioned on slashdot. Hopefully, things will return to normal soon.
• Installing Rails
  2005-01-25 09:34:58  APC [View]
  
  
  Okay. I'll keep trying.
  
  I guess I've heard enough good things about Ruby to justify some more effort.
  
  Cheers, APC
• Installing Rails
  2005-01-25 10:24:57  Curt Hibbs | [View]
  
  
  I read your initial posting too quickly, I should have noticed that you mentioned your companies firewall. If this includes a proxy for web access, then you'll need to tell RubyGems about this when downloading/installing Rails. Use this:
  
  gem install -p http://<proxy-url> rails
  
  Good luck!
• Installing Rails
  2005-01-26 00:36:12  APC [View]
  
  
  Thanks Curt. Passing the proxy URL was all I needed to do.
  
  Now I have the answer I realise that I could have googled for it and solved the problem yesterday. Doh!
  
  Have a better one, APC
  
  
• Installing Rails
  2005-11-25 12:49:48  Okki [View]
  
  
  You can also make an environment variable called http_proxy. I have set this in my environment variables and it worked immediately.
  
  http_proxy=http://your.proxy.host:port/
• Installing Rails
  2005-12-02 15:30:19  lena_ [View]
  
  
  If you are behind a firewall and http proxy is not available, you can download "rails" gem (rails*.gem) from http://rubyforge.org and install it using local gem installation.
  
  You may need to get other gems (.gem files) before rails installation succeeds. For instance, I had to also get all of these:
  rake
  activesupport
  activerecord
  actionpack
  actionmailer
  actionwebservice
  
  and install them in this order before finally installing rails:
  
gem install rake --include-dependencies
gem install activesupport --include-dependencies
...
gem install rails --include-dependencies

  
  Hope this helps.