Roger,

Most of the tutorials around didn't consider the "Windows users
minority". That is a problem I pretend to solve (or minimize at
least), with the TrainerOnRails project:

http://www.traineronrails.com/

That way, the commands presented in these tutorials are not exactly
the ones we will use in Windows.

On the other hand, this one is not particular clear the way they show
the database configuration section.

Suggestion:

delete the blog folder, open a command window on your apps folder and
do:

E:\TEMP>rails blog
E:\TEMP>cd blog
E:\TEMP\blog>ruby script/server

Then start your browser and call:

http://localhost:3000

It must work that way.

I strongly suggest you to follow this tutorial:

http://www.buildingwebapps.com/podcasts

In your case, take a look at the first 8 lessons and check if you are
ready with all you need to get this done.

Then go forward with the next lessons 9 to 23. In the end you will
have done a complete CMS.

It works for me.

All the best.


On Oct 2, 6:15 pm, Roger_jg <[email protected]> wrote:
> Hello,
>
> Pure newbie question.
> After installeing Ruby, Rail and al the gems I am following the
> tutorial herehttp://guides.rubyonrails.org/getting_started.html
>
> I start a server with Mongrel and it seems to be working, but when I
> try to acceshttp://localhost:3000i get a firefox error:
> Firefox can't establish a connection to the server at localhost:3000
>
> I work under Vista with Ruby the latest one-click install ruby.
>
> I have tried with Netbeans and with WEBrick but same problem.
>
> There is a similar question on this group but no answer that match my
> problem.
>
> Advice welcome.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to