Don't cd into the script dir, instead call it from the project root:

ruby script/server

On Jun 2, 11:46 pm, Yasir <[email protected]> wrote:
> Hi,
>
> I am new to Ruby, while running a project I get the following errors:
>
> C:\cairns\cairns\cairns\script>ruby server
> => Booting WEBrick...
> server: No such file or directory - uname
> C:/cairns/cairns/cairns/app/models/node.rb:74:in `get_hostname': You
> have a nil
> object when you didn't expect it! (NoMethodError)
> The error occurred while evaluating nil.chop
>         from C:/cairns/cairns/cairns/app/models/node.rb:60:in
> `initialize'
>         from ./../config/../config/environment.rb:65:in `new'
>         from ./../config/../config/environment.rb:65
>         from C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:
> 31:in `ge
> m_original_require'
>         from C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:
> 31:in `re
> quire'
>         from C:/Ruby/lib/ruby/gems/1.8/gems/activesupport-1.4.4/lib/
> active_suppo
> rt/dependencies.rb:495:in `require'
>         from C:/Ruby/lib/ruby/gems/1.8/gems/activesupport-1.4.4/lib/
> active_suppo
> rt/dependencies.rb:342:in `new_constants_in'
>         from C:/Ruby/lib/ruby/gems/1.8/gems/activesupport-1.4.4/lib/
> active_suppo
> rt/dependencies.rb:495:in `require'
>          ... 6 levels...
>         from C:/Ruby/lib/ruby/gems/1.8/gems/rails-1.2.5/lib/commands/
> server.rb:3
> 9
>         from C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:
> 31:in `ge
> m_original_require'
>         from C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:
> 31:in `re
> quire'
>         from server:3
>
> Need Help!
>
> Kind Regards,
--~--~---------~--~----~------------~-------~--~----~
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