Downgrading from Ruby 2.1.6 to Ruby 1.8.7

rubyonrails-talk
1

Hi All,

Our client wants to downgrade our e-commerce website from Ruby 2.1.6 to Ruby 1.8.7. I know this makes no sense. But when we got the requirement to do the website, we developed using the latest version 2.1.6 but the client wants to have the website in the old version, since his server is not compatible with new one (MAKES SENSE?, but no other way).

Could anyone help us? Is there any other tool to do the migration from 2.1.6 to 1.8.7. ??

Looking for help from you guys. Thanks in advance.

2

Hi All,

Our client wants to downgrade our e-commerce website from Ruby 2.1.6 to Ruby 1.8.7. I know this makes no sense. But when we got the requirement to do the website, we developed using the latest version 2.1.6 but the client wants to have the website in the old version, since his server is not compatible with new one (MAKES SENSE?, but no other way).

Could anyone help us? Is there any other tool to do the migration from 2.1.6 to 1.8.7. ??

I don't think there is any particular tool to do this. In addition this will require you to downgrade to rails 3.2 which will be completely unsupported when rails 5 is released in the autumn. Ruby 1.8.7 is also not receiving any security patches.

Fred

3

Frederick Cheung wrote in post #1177922:

4

Hi All,

Our client wants to downgrade our e-commerce website from Ruby 2.1.6 to

Ruby 1.8.7. I know this makes no sense. But when we got the requirement

to do the website, we developed using the latest version 2.1.6 but the

client wants to have the website in the old version, since his server is

not compatible with new one (MAKES SENSE?, but no other way).

Ruby will compile on fairly near anything with a sensible C compiler and the configure program. If the server is so outdated that it doesn’t have that, there are other problems.

There are a variety of tools for allowing multiple Ruby versions to coexist on one system; you should strongly suggest using one.

1.8.7 was end-of-lifed (no further updates from the core team) in June 2013. It received a followup set of security patches in December 2013 to address CVE-2013-4164, but those were from a team at Heroku. Unless you or your client’s team have the capability to evaluate 1.8.7’s vulnerability to the subsequent 18 months of reported vulnerabilities, you are taking a massive security risk.

Apart from security, the other big reason to encourage a Ruby upgrade vs. an application rewrite is that the Ruby upgrade is straightforward - even if the server is particularly badly-configured, it’s still ultimately a well-documented process to get Ruby to build. Rewriting the application is much trickier.

If none of those arguments work, at least post the name of the company on here. I’d like to make sure I never give them my credit card number…

–Matt Jones

5

Hi Matt,

Thanks for your response.

We rejected the request from the client and returned back the advance amount they paid and informed like "we would like to stick with our standard and do not make our project as a buggy or run our website without any security. "

Thanks a lot for everyone.