I have a ruby/rails app that is still stuck on ruby 2.3.7 and uses Passenger 5.3.3. I wanted to upgrade the Passenger version to the latest safe/stable version that still works with ruby 2.3.7
I went through the release notes of each 6.x release and noticed this in the 6.0.9 release notes:
https://github.com/phusion/passenger/releases/tag/release-6.0.9
ruby:
2.3.8 → removed
2.5.8 → 2.5.9
...
"However", even when i installed a more recent version of Passenger (6.0.14), it seemed to work with Ruby 2.3.7, so i'm quite confused about that those release changelogs are talking about when they mention dropping support for older versions of ruby.
NOTE: I did have to set PassengerDisableAnonymousTelemetry on in 6.0.14 to resolve a crashing issue.
Thought i'd post this here since i got confirmation directly from Phusion
that Passenger v6.0.14 is compatible with Ruby 2.3.7
Related
Hi I am wanting to install my website on a site5.com website but I am having difficulty. The ruby version on the actual site is 1.8.7 but the ruby version I use on my local computer is 1.9.3. How do I upgrade to ruby 1.9.3 without the use of sudo, apt-get install, and apt-get update?
If anyone knows some ways to get in without having to use sudo or the above, I would be very greatful for an answer to this problem.
Basically, I don't think you can at the moment. But as of a few weeks ago, it looks like they're starting to convert to 1.9.3 (emphasis added):
We will begin the process of updating all servers to a newer version of Phusion Passenger (the 4.0 branch) in November. That deployment will allow you to use any version of Ruby — including 1.9 and 2.0 — inside your Rack-based applications (e.g. Rails).
We will then begin work on changing the default Ruby across our entire fleet from Ruby 1.8.7 to 1.9.3. You will receive ample notification for this change, but if your application only functions on Ruby 1.8.7, you will be able to change the Ruby version per-application and per-account (via .htaccess) using the PassengerRuby option available in Phusion Passenger 4. You can then compile your own version of Ruby 1.8 inside of your account for your legacy applications.
I m working on a project which was developed by another developer. Right now my job is to fix the bugs and all the necessary things. After all those things successfully done when i started to work for deployment on site5.com i got to know here that they ve not upgraded the ruby version. Still they are using ruby 1.8.7. There is a tutorial to upgrade the system to rails 3 but m not able to do that. The rails version installed on the server is 2.3.16.
When the code was given to me i bundle installed it with new version 1.9.3 and then i fixed few bugs which was a syntax error because of that syntax deprecation in 1.9.3. Now i ve asked to the client that there may be some compatibility issues if i go with the installation. Now what should i do? Should i go with the installation or suggest him some other hosting website.
since phusion 4 is stable now (allowing multiple rubies), and ruby 1.8 is considered 'legacy' by phusion developers (see their blog), doing any fixes for ruby 1.8.x seems to be a waste of time.
Changing ruby version requirements would break the application on site5, if they're really still on 1.8.x .
I recently upgraded to ruby 1.8.7. i'm running Rails 2.3.5 and rubyGems 1.5.2.
ever since I upgraded, every time I want to start the server, i get:
undefined local variable or method `version_requirements' for #<Rails::GemDependency:0x1022cc1c8> (NameError)
this post here advises to downgrade rugyGems to a version below 1.5.0.
downgrading doesn't seem to be the right solution..should I maybe be upgrading Ruby or Rails instead?
Also, if I upgrade to the latest ruby (1.9.2) and rails (3.0)..will my application break?
I have a very large application and can't figure out how to upgrade it without breaking the application..
That thing about version_requirements is a bug in rubygems - confirmed by their creators.
I've also participated in the bug report on the rubygems :)
gem update --system 1.5.0
performs a graceful downgrade until this is fixed.
I ran into this issue with some Rails 2.x applications and once also with 3.0.4 application, but with different error message, again, downgrading rubygems solved it.
You should use RVM so you can have both, 1.8 and 1.9.2 Ruby versions, running and you can be working with rails 2.3.x and rails 3.x the way that you want
running two rails 2.3.8 apps on two virtual servers in ubuntu 8.04 with apache and passenger. the ruby version is 1.8.6
we are upgrading one of the apps to rails 3.0.4. my understanding is that we need ruby 1.8.7 to run the app. with this version of ubuntu we will need to compile ruby 1.8.7 manually.
never compiled manually before. if you know of any resources i should check out that would be great.
i have not been able to determine the version of passenger and am trying to make sure it will be compatible with rails 3.0.4. any suggestions?
the application we are leaving in 2.3.8 is our core business application and i need to make sure i don't mess it up.
Thanks!
Just use RVM. Almost everybody use it now.
Early Passenger versions for Apache had some bugs so my suggestion is to simply upgrade Passenger to the newest version.
i have a production and a development machine, both running ubuntu 8.10 and both are running the latest phusion passenger. as i am using ruby 1.9.1 on my local development machine on osx, i wondered if people out there are already using phusion passenger with ruby 1.9.1 or even 1.9.2 already?
if so, please tell us your setup!
furthermore, is ther a way to run both ruby 1.8.7 (ree) and 1.9.1 with phusion passenger on apache?
thanks for any pointers, i could not find any hints on this anywhere...
Yes it's officially supported since some 2.2.x release for which I can't remember the exact number. It was written in the release notes. The past few 2.2 releases have only continued to add 1.9-related bug fixes. The upcoming 3.0 release will officially support 1.9.2 as well (though this doesn't imply that 1.9.2 doesn't already work).
You can't run two Ruby versions simultaneously yet but it's on the todo list.