# Getting Started with Rails - Encountered beginning problem

**URL:** <https://www.ruby-forum.com/t/getting-started-with-rails-encountered-beginning-problem/186154>\
**Category:** Rails\
**Created:** [April 1, 2010, 10:05am UTC](https://www.ruby-forum.com/t/getting-started-with-rails-encountered-beginning-problem/186154 "2010-04-01T10:05:44Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Soulzityr](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/34f0e0/32.png) [@Soulzityr](https://www.ruby-forum.com/u/Soulzityr)\
**Post date:** [April 1, 2010, 10:05am UTC](https://www.ruby-forum.com/t/getting-started-with-rails-encountered-beginning-problem/186154/1 "2010-04-01T10:05:44Z")

</div>

Hello, I bought a book called “Head First Rails” and it’s great,  
starting off with giving me a few commands to instantly begin diving  
into learning Rails. However, I ran into a problem that I’m not quite  
sure how to fix.

So I’m following along the beginning exercise where I did the  
following commands. Btw, I’m using Windows 7 cmd.

> rails tickets  
> cd tickets  
> ruby script/server

Now, step 3 works and I can even go to [http://localhost:3000/](http://localhost:3000/) to look  
at some randomly generated Ruby Introduction Page, but I can’t type in  
cmd anymore. The output looks like this

* * *

=\>booting WEBrick  
=\>Rails 2.3.5 application starting on [http://0.0.0.0:3000](http://0.0.0.0:3000)  
=\>call with -d to detach  
=\>Ctrl-c to shutdown server  
[TIMESTAMP] INFO WEBrick 1.3.1  
[TIMESTAMP] INFO ruby 1,8,6 \<2008-08-11\> [i386-mswin32]  
[TIMESTAMP] INFO WEBrick:HTTPServer#start: pid=6556 port=3000

* * *

the next command line never appears and I can’t type. Do I need to  
ctrl-c to shutdown server if i want to run anymore commands, like  
scaffolds?

---

<div class="post-metadata">

**Author:** ![Soulzityr](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/34f0e0/32.png) [@Soulzityr](https://www.ruby-forum.com/u/Soulzityr)\
**Post date:** [April 1, 2010, 10:08am UTC](https://www.ruby-forum.com/t/getting-started-with-rails-encountered-beginning-problem/186154/2 "2010-04-01T10:08:05Z")

</div>

On Apr 1, 5:36 am, Soulzityr [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> the next command line never appears and I can’t type. Do I need to  
> ctrl-c to shutdown server if i want to run anymore commands, like  
> scaffolds?

This is completely normal. You can’t type a new command in this  
console session because the previous command is still running. You can  
either kill the server or open up a new command prompt or run the  
server in the background (with the -d option)

Fred

---

<div class="post-metadata">

**Author:** ![Soulzityr](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/34f0e0/32.png) [@Soulzityr](https://www.ruby-forum.com/u/Soulzityr)\
**Post date:** [April 1, 2010, 10:13am UTC](https://www.ruby-forum.com/t/getting-started-with-rails-encountered-beginning-problem/186154/3 "2010-04-01T10:13:21Z")

</div>

This is normal behavior  
With the ruby script/server command you actually started a web server  
process.  
Now that process is holding your console (the Windows 7 cmd)  
So you should start a new console and you can type all others commands.  
In the first console, you can watch the result of the server operations

by the way, this book is excellent !!

good luck

Le 1 avr. 2010 à 06:36, Soulzityr a écrit :