A few days ago, ruby 1.9.3p327 was released to handle a possible DoS issue.
Is there a way to upgrade ruby version in Heroku? right now I have ruby 1.9.3p286 (2012-10-12 revision 37165) [x86_64-linux] when I put ruby "1.9.3" in my gemfile
Update
Heroku updated the ruby version on cedar to p327
You can't specify a patch number in your Gemfile, you can only set the version number. Heroku will manage the patch levels so you will need to wait until they upgrade it.
See
https://devcenter.heroku.com/articles/ruby-support
https://devcenter.heroku.com/articles/ruby-versions
Related
I have almost finished my first Ruby on Rails application, i have used Ruby 2.1.2 and Rails 4.2.4.. then i want to deploy it, the hosting i took gave me 1month trial but they have installed CPanel 11 (it has rails 2.3.18 by default)
but when i try to install the rails 4.2.4 gem it gives me this:
> Error installing rails: i18n requires Ruby version >= 1.9.3.
My questions are:
Is there a way to update the ruby?
Would i have any trouble if they just update to 1.9.3 when i have used 2.1.2?
this is a screenshot from the gems in the cpanel
Recently I had to upgrade my Ruby version to a higher one and I was in a very similar situation like yours.
I used rvm for this.
Use rvm for listing the ruby version with the following command:
rvm list known
Then upgrade ruby with: rvm install version_of_your_choice
Also, search the internet for tutorials. StackOverflow has all the answers.
Background
On my local machine, I tried installing the 'bullet' gem via my gemfile, and bundle seemed to go without incident, however upon restarting my app passenger began throwing the error Invalid gemspec for uniform_notifier. It seems someone else had this issue and the suggested resolution on StackOverflow said to update RubyGems by running:
The issue
gem update --system
This produced no error messages upon running, however now none of apps will start. They all give the same vague Passenger error:
PhusionPassenger::UnknownError
There was an error in your Gemfile, and Bundler cannot continue. (Bundler::GemfileError)
I removed 'bullet' from my gemfile so it's now back in a state when it was working yesterday, so I don't think there can be an error in my gemfile. Furthermore, all of my other apps are now broken and their gemfiles haven't changed at all.
For reference:
ruby -v
ruby 1.9.2p0 (2010-08-18 revision 29036) [x86_64-darwin10.5.0]
rails -v
Rails 3.2.6
rvm --version
rvm 1.1.4 by Wayne E. Seguin
And when I do gem list for the global and local gemsets, it shows bundler 1.1.0 installed.
Edit: I should also mention that running rails s starts up a WEBrick server just fine and I can access my apps at localhost:3000, so it's only under Passenger that this error crops up.
Have you committed your Gemfile.lock?
I was able to fix this by rolling back rubygems-update to the previously installed version by running
gem update --system 1.8.11
At which point all of my apps began working again. I'm still not sure what the problem was, and will gladly switch the accepted answer from my own to someone who can provide more insight into why updating rubygems-update would break Passenger integration.
I wish someone from Phusion Passenger would give a definitive answer but just wanted to say that I've experienced the same thing. Updating rubygems has broken passenger-nginx integration for us and requires recompiling the passenger-nginx module. Not sure why this would be. My speculation is that the module is somehow compiled with a hard reference to a specific version of rubygems.
I am trying to install a rails 1.2.3 app on my machine. My machine is currently using rails 3.2.6 , ruby 1.9.3 and windows 7. While trying to use 'RAKE', I am getting the following error
WARNING: 'require 'rake/rdoctask'' is deprecated.
Please use 'require 'rdoc/task' (in RDoc 2.4.2+)' instead.
How shall I figure out the problem in order to be able to use my application.
In your Rakefile you should change the require statements as rake demands it. There might be follow up errors so it would be best to update Rake to match your rails version.
I'm using RVM on my development machine for my Ruby on Rails application which works really well. My question is should I (can I) use RVM on my live server for deployment?
I already have the web app up on a live server using Passenger but I have just installed Ruby and all the gems on the system.
Are there any performance issues with RVM and is there much that I would need to do with my Apache web server to get it up and running?
Thanks
Performance of ruby compiled manually and with RVM - should be the same (unless you uses patches like patchexpress or falcon).
You can use RVM for deployment - you can do it together with updating ruby version / patchlevel, it's very important to use the latest patchlevel as it contains important fixes for ruby - including security fixes.
As for integration of RVM compiled Rubies - read the docs: https://rvm.io/integration/passenger/
I using the rails by Instantrails on windows.It can run well before I update the rails version to rails 3 .
The error message is :
E:\InstantRails-2.0-win\rails_apps\myproject>rails server
E:/InstantRails-2.0-win/ruby/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/bundler/lo
ckfile_parser.rb:48:in parse_source': undefined method[]' for nil:NilClass (N
oMethodError)
from E:/InstantRails-2.0-win/ruby/lib/ruby/gems/1.8/gems/bundler-1.0.0/l
ib/bundler/lockfile_parser.rb:20:in send'
from E:/InstantRails-2.0-win/ruby/lib/ruby/gems/1.8/gems/bundler-1.0.0/l
ib/bundler/lockfile_parser.rb:20:ininitialize'
from E:/InstantRails-2.0-win/ruby/lib/ruby/gems/1.8/gems/bundler-1.0.0/l
ib/bundler/lockfile_parser.rb:14:in each'
from E:/InstantRails-2.0-win/ruby/lib/ruby/gems/1.8/gems/bundler-1.0.0/l
ib/bundler/lockfile_parser.rb:14:ininitialize'
from E:/InstantRails-2.0-win/ruby/lib/ruby/gems/1.8/gems/bundler-1.0.0/l
ib/bundler/definition.rb:43:in new'
from E:/InstantRails-2.0-win/ruby/lib/ruby/gems/1.8/gems/bundler-1.0.0/l
ib/bundler/definition.rb:43:ininitialize'
What cause this error?
I found that answer,because the old version project can't run on the new version.
You're troubling the trouble by using a legacy environment like InstantRails for rails3.
InstantRails hasn't been updated for nearly 3 years and its latest version includes ruby 1.8.6 which is incomplatible with rails 3.
From the official Ruby on Rails website:
We recommend Ruby 1.8.7 or Ruby 1.9.2 for use with Rails. Ruby 1.8.6 and earlier are not supported, neither is version 1.9.1
If you really insist on using windows as a development environment, the recommended way of getting rails 3 to work on Windows right now is to install ruby via the Windows installer: http://rubyforge.org/frs/?group_id=167 and then just install RubyGems by running its installation script and afterwards install rails3 as gem.