Rails Server's case sense dilemma

Hi ,

I found something strange with Mongrel Server ,

When i started my application with

RUBY SCRIPT/SERVER -P 3002

application starts successfully but can’t render anything on browser.

gives error => Unable to connect.

When i starts with commanf

ruby script/server -p 3002

Application runs successfully .

any comment ?

Hi,

Let me guess, you are using windows?
That’s the only reason that RUBY SCRIPT/SERVER would actually work, as
on
any other OS, it would force you to use ruby script/server to start the
server.
That said, the -P isn’t a valid option, so the script is ignoring it and
starting the server on the default port (3000).

Cheers
Simon

On Mon, 24 Aug 2009 13:00:24 +0800, Ruby on Rails

Simon M. wrote:

Hi,

Let me guess, you are using windows?
That’s the only reason that RUBY SCRIPT/SERVER would actually work, as
on
any other OS, it would force you to use ruby script/server to start the
server.
That said, the -P isn’t a valid option, so the script is ignoring it and
starting the server on the default port (3000).

Cheers
Simon

On Mon, 24 Aug 2009 13:00:24 +0800, Ruby on Rails

Thanks ,
Simon . You are right .