Update VirtualRails to Rails 3.1.1 and Ruby 1.9.2

Has anyone managed to update VirtualRails to Rails 3?

I’ve managed to get as far as installing RVM, creating a new project
folder but when I try to run the rails server I get this message:

virtualrails@jay ~/Sites/test_project $ rails server
/home/virtualrails/.rvm/gems/ruby-1.9.2-p290/gems/execjs-1.2.9/lib/execjs/runtimes.rb:47:in
autodetect': Could not find a JavaScript runtime. See https://github.com/sstephenson/execjs for a list of available runtimes. (ExecJS::RuntimeUnavailable) from /home/virtualrails/.rvm/gems/ruby-1.9.2-p290/gems/execjs-1.2.9/lib/execjs.rb:5:inmodule:ExecJS
from
/home/virtualrails/.rvm/gems/ruby-1.9.2-p290/gems/execjs-1.2.9/lib/execjs.rb:4:in
<top (required)>' from /home/virtualrails/.rvm/gems/ruby-1.9.2-p290/gems/coffee-script-2.2.0/lib/coffee_script.rb:1:inrequire’
from
/home/virtualrails/.rvm/gems/ruby-1.9.2-p290/gems/coffee-script-2.2.0/lib/coffee_script.rb:1:in
<top (required)>' from /home/virtualrails/.rvm/gems/ruby-1.9.2-p290/gems/coffee-script-2.2.0/lib/coffee-script.rb:1:inrequire’
from
/home/virtualrails/.rvm/gems/ruby-1.9.2-p290/gems/coffee-script-2.2.0/lib/coffee-script.rb:1:in
<top (required)>' from /home/virtualrails/.rvm/gems/ruby-1.9.2-p290/gems/coffee-rails-3.1.1/lib/coffee-rails.rb:1:inrequire’
from
/home/virtualrails/.rvm/gems/ruby-1.9.2-p290/gems/coffee-rails-3.1.1/lib/coffee-rails.rb:1:in
<top (required)>' from /home/virtualrails/.rvm/gems/ruby-1.9.2-p290/gems/bundler-1.0.21/lib/bundler/runtime.rb:68:inrequire’
from
/home/virtualrails/.rvm/gems/ruby-1.9.2-p290/gems/bundler-1.0.21/lib/bundler/runtime.rb:68:in
block (2 levels) in require' from /home/virtualrails/.rvm/gems/ruby-1.9.2-p290/gems/bundler-1.0.21/lib/bundler/runtime.rb:66:ineach’
from
/home/virtualrails/.rvm/gems/ruby-1.9.2-p290/gems/bundler-1.0.21/lib/bundler/runtime.rb:66:in
block in require' from /home/virtualrails/.rvm/gems/ruby-1.9.2-p290/gems/bundler-1.0.21/lib/bundler/runtime.rb:55:ineach’
from
/home/virtualrails/.rvm/gems/ruby-1.9.2-p290/gems/bundler-1.0.21/lib/bundler/runtime.rb:55:in
require' from /home/virtualrails/.rvm/gems/ruby-1.9.2-p290/gems/bundler-1.0.21/lib/bundler.rb:122:inrequire’
from /home/virtualrails/Sites/test_project/config/application.rb:7:in
<top (required)>' from /home/virtualrails/.rvm/gems/ruby-1.9.2-p290/gems/railties-3.1.1/lib/rails/commands.rb:52:inrequire’
from
/home/virtualrails/.rvm/gems/ruby-1.9.2-p290/gems/railties-3.1.1/lib/rails/commands.rb:52:in
block in <top (required)>' from /home/virtualrails/.rvm/gems/ruby-1.9.2-p290/gems/railties-3.1.1/lib/rails/commands.rb:49:intap’
from
/home/virtualrails/.rvm/gems/ruby-1.9.2-p290/gems/railties-3.1.1/lib/rails/commands.rb:49:in
<top (required)>' from script/rails:6:inrequire’
from script/rails:6:in `’

Running VirtualBox 3.2.12 on Windows 7 64bit.

Thanks in advance.
Jason.

Download this PDF tutorials on installing RoR and look for the no.10
section and how to solve it:

Mircea

Thanks for the link, Mircea.

I’ve gone through the pdf with the Virtual Rails install (Linux Mint 8)
and then with a completely fresh install of Linux Mint 11 but when I
reach the bit where it says:

no such file to load – openssl (trying to run rails server)

Then typing: “$ rvm package install openssl” just gives me

"ERROR: Unrecognized command line arguement: ‘package’ (see: ‘rvm
usage’)

Is there an alternative to this? A reason ‘package’ isn’t an arguement
for RVM anymore?

Thanks again.

Thanks Hassan, it was “pkg” not “package” - where I come from its called
a typo!

Anyway, turned out that a line of earlier code hadn’t been executed
fully on my install (copy and paste issues). Got it working great now.

On Thu, Nov 10, 2011 at 10:58 PM, Jason W. [email protected]
wrote:

Then typing: “$ rvm package install openssl” just gives me

"ERROR: Unrecognized command line arguement: ‘package’ (see: ‘rvm
usage’)

Is there an alternative to this? A reason ‘package’ isn’t an arguement
for RVM anymore?

The above message says “see: ‘rvm usage’” – did you? I’m guessing
not, because the answer to your question is there.


Hassan S. ------------------------ [email protected]

twitter: @hassan