Setting up ROR on my VPS

Does the script/console need to be working on the production server?

It doesn’t work on my server. I get the following error when I try to
use it. I was just wondering if this is an indication that ROR isn’t
installed properly on my server.

[root@vps test]# ./script/console
Loading development environment.
/usr/local/lib/ruby/1.8/irb/completion.rb:10:in require': no such file to load -- readline (LoadError) from /usr/local/lib/ruby/1.8/irb/completion.rb:10 from /usr/local/lib/ruby/1.8/irb/init.rb:252:inrequire’
from /usr/local/lib/ruby/1.8/irb/init.rb:252:in load_modules' from /usr/local/lib/ruby/1.8/irb/init.rb:250:ineach’
from /usr/local/lib/ruby/1.8/irb/init.rb:250:in load_modules' from /usr/local/lib/ruby/1.8/irb/init.rb:21:insetup’
from /usr/local/lib/ruby/1.8/irb.rb:54:in `start’
from /usr/local/bin/irb:13

Thanks in advance for any insight,

George

Does the script/console need to be working on the production server?
No, script/console does not need to work for your rails application to
run.

To fix this issue you need to install the readline-devel package, if
you are using a distro with yum, this is how you would fix this:

yum install readline-devel
cd /path/to/ruby/source/ext/readline
ruby extconf.rb
make
make install


Joe C.

As Joe already sad, the rails console do not has to work in order that
your Rails web application run.

I suppose that the real question was does rails console run on
production servers.
The rails console should be operational and at you service on any
platform with properly installed ruby and ruby on rails.

The error message that is presented is from missing gem.
You should be aware of all gems that your application use or you’ll be
seeing this kind of messages a lot.
We all have been in your schusses at one time or another. :slight_smile:

Does your app work in production? You might need to pass the
RAILS_ENV=production before your ./script/console or make sure you are
not missing any gems in your server.

Good luck,

Peter

On Oct 6, 5:13 pm, George G. [email protected]