After install with the installer, getting error in running the "blog" example from http://guides.rubyonrails.org/getting_started.html

[Ivy (Xiao) Peng]

Firstly, I am completely new to ROR. That is why I am following the "blog" example from http://guides.rubyonrails.org/getting_started.html.

Secondly, running the installer didn't generate any error in any obvious way. But errors in running the blog example led me to think some gems seems to missing from installation.

Errors:

1. running "rails new blog" right after the installation, it seems to run "bundle update" implicitly. It aborts with this eror:

Fetching source index from https://rubygems.org/

Could not fetch specs from https://rubygems.org/

I tried switching the source to 'http://bundler-api.herokuapp.com' in Gemfile, no luck.

Then tried add "gem builder" to the Gemfile as suggested by a post from the web. no luck.

With the "bundle update" failure, some gems are missing. Subsequent steps failed and manual workaround didn't work.  Pls see details below

My env:

a. Window XP

b. behind a corporate firewall. I can "ping rubygems.org". Output is as below. Although timeout, it seems able to solve the hostname.

Pinging rubygems.org [54.245.255.174] with 32 bytes of data:

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Ping statistics for 54.245.255.174:

    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

But I not "ping http://rubygems.rog" (with or without s). It would complain "could not find host https://rubygems.org"

Question:

a. Should uglifier have been installed by the installer by default?

b. How to get around the Could not fetch specs from https://rubygems.org error? Is it the firewall causing issue? 

Help pls?

Details on troubleshooting effort:

Below is what I have tried. It is not going anywhere. Please help

1. "rake db:create" cannot complete as it complains uglifier missing

[31mCould not find gem 'uglifier (>= 1.0.3) x86-mingw32' in the gems available

n this machine.←[0m

[33mRun `bundle install` to install missing gems.←[0m

2. tried "bundle update". It gives the following error

Fetching source index from https://rubygems.org/

Could not fetch specs from https://rubygems.org/

3. tried manually download uglifier and install. This in turn asked for therubyracer, ref, and libv8.

4. installing libv8 3.16.14.1generates "Failed to build gem native extension." error and it complains Python 2 is missing. 

4.1. installed Python and added it to user and system variable PATH. But it didn't make a difference.

5. installing libv8 3.11.8.12.generates error complaining about no gmake. 

At this point, I gave up as from what I read, it seems libv8 is not supported on win. 

[Evan Machnic]

Hi,

Try changing the source from https://rubygems.org to http://rubygems.org. Seems like your firewall may be getting in the way.

In terms of therubyracer stuff, try installing Node.js for the libv8 dependency; you should not neet to install Python.

Please note that many tutorials are written for Unix environments and will need to be adapted for a Windows environment. StackOverflow and Google are your friends.

Thanks,

Evan Machnic

---

Evan B. Machnic // Application Support

The Leading Platform as a Service

Office: 415.994.5365

Skype: evan.ey

Twitter:  @emachnic

Distill: A conference to explore the development of inspired applications

Tickets are now on sale, be sure to get yours before they sell out!

---

--
You received this message because you are subscribed to the Google Groups "RailsInstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email to railsinstalle...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Ivy (Xiao) Peng]

Evan,

I should have been more specific in my original post. The installer gave me all those issues is Windows Ruby 1.9.

After I posted my question, I decided to try installer 1.8. I am able to bring up the "hello rails" page (hooray!) and it has been a smooth sail.

Thanks for your reply. I have tried the "http://". That didn't help. If I had to work with 1.9 for some reason, I will certainly try the node.js solution.

Regards

-Ivy