Jump to content

The ultimate community for Ruby on Rails developers.


Photo

Upgrading rails application

rails 3.0 rails 3.2 upgrade rails

  • Please log in to reply
8 replies to this topic

#1 Giacomo

Giacomo

    Signalman

  • Members
  • 13 posts
  • LocationBologna

Posted 19 August 2013 - 10:39 AM

Hi All,

Is there an easy (fast and effortless) way to upgrade a rails application from rails 3.0 to rails 3.2?

 

Thanks



#2 Ohm

Ohm

    Guard

  • Members
  • 179 posts
  • LocationCopenhagen

Posted 19 August 2013 - 11:41 AM

You might need to be a bit more specific. 

 

You can upgrade your Rails version in your Gemfile just by changing the version

<snippet>
source 'https://rubygems.org'
ruby '2.0.0'
gem 'rails', '3.2.14'
<snippet>

... and then running bundle afterwards.

 

Some things will break, so you'll need to take care of this before deploying the upgraded version to production.


  • james likes this

Blog: http://ohm.sh | Twitter: madsohm


#3 Giacomo

Giacomo

    Signalman

  • Members
  • 13 posts
  • LocationBologna

Posted 19 August 2013 - 12:01 PM

Thanks for you reply but...

What about assets?


--

G.


#4 Jamie

Jamie

    Controller

  • Moderators
  • 114 posts
  • LocationThe UK

Posted 19 August 2013 - 03:37 PM

Thanks for you reply but...

What about assets?

 

Like Ohm could you provide a bit more detail what you mean about upgrading, if you have a question about assets - What is it that you would like to know?

 

:)


Rails developer based in Newcastle, UK.
Web app owner - Twitter lover

#5 noz

noz

    Signalman

  • Members
  • 21 posts

Posted 19 August 2013 - 06:20 PM

These links might be of some use:

 

Upgrading 3.0  -> 3.1

Upgrading 3.1 -> 3.2

 

IMPORTANT: Ensure that you upgrade to the latest subversion to get all the security fixes, I believe it's up to 14 now (so 3.2.14). 



#6 Ohm

Ohm

    Guard

  • Members
  • 179 posts
  • LocationCopenhagen

Posted 19 August 2013 - 06:30 PM

These links might be of some use:

 

Upgrading 3.0  -> 3.1

Upgrading 3.1 -> 3.2

 

IMPORTANT: Ensure that you upgrade to the latest subversion to get all the security fixes, I believe it's up to 14 now (so 3.2.14). 

 

Why would you do it in two steps? Wouldn't you be able to do it from 3.0 -> 3.2(.14) just as easy?


Blog: http://ohm.sh | Twitter: madsohm


#7 sathishror

sathishror

    Passenger

  • Members
  • 1 posts

Posted 07 September 2013 - 11:56 AM

Hi all,

 

I am upgrading rails 2.3.18 to 3.0.0... after modifying all the files using "rake rails:upgrade:check"

 

Old Rails generator API
A plugin in the app is using the old generator API (a new one may be available at http://github.com/tr...ils3-generators).
More information: http://blog.platafor...s-3-generators/

The culprits:
    - vendor/plugins/resource_controller/generators/
    - vendor/plugins/resource_controller/generators/scaffold_resource/
    - vendor/plugins/rspec-rails/generators/
    - vendor/plugins/rspec-rails/generators/rspec_scaffold/
    - vendor/plugins/rspec-rails/generators/integration_spec/
    - vendor/plugins/rspec-rails/generators/rspec_controller/
    - vendor/plugins/rspec-rails/generators/rspec_model/
    - vendor/plugins/rspec-rails/generators/rspec/

 

Ref url is broken, can any one help on this ..



#8 levberlin

levberlin

    Passenger

  • Members
  • 5 posts

Posted 19 September 2013 - 08:44 PM

The main difference is the asset pipeline in 3.1, so you'll have to rejig a few things to enable that and ensure you're using that appropriately. It'll improve your app's performance a good deal as well.



#9 RichOnRails

RichOnRails

    Signalman

  • Members
  • 10 posts

Posted 05 November 2013 - 11:51 PM

Hi all,

 

I am upgrading rails 2.3.18 to 3.0.0... after modifying all the files using "rake rails:upgrade:check"

 

Old Rails generator API
A plugin in the app is using the old generator API (a new one may be available at http://github.com/tr...ils3-generators).
More information: http://blog.platafor...s-3-generators/

The culprits:
    - vendor/plugins/resource_controller/generators/
    - vendor/plugins/resource_controller/generators/scaffold_resource/
    - vendor/plugins/rspec-rails/generators/
    - vendor/plugins/rspec-rails/generators/rspec_scaffold/
    - vendor/plugins/rspec-rails/generators/integration_spec/
    - vendor/plugins/rspec-rails/generators/rspec_controller/
    - vendor/plugins/rspec-rails/generators/rspec_model/
    - vendor/plugins/rspec-rails/generators/rspec/

 

Ref url is broken, can any one help on this ..

 

Ouch...2.3.18 to 3.x?  While it might be a bit more work, you might be better off creating a new project skeleton and porting your old code in.  SOOO many things have changed between 2.x and 4.x it's crazy.  Even if you did manage to upgrade the project, you wouldn't be using any of the Rails 3 or Rails 4 features.  

 

As for the original poster, you can disable the assets pipeline if you wish to make the transition easier.  However, if you are going to upgrade to 3.2, I'd recommend just going all the way to 4.  The Ruby on Rails website has a great upgrade guide available that should be of assistance:  http://edgeguides.ru...y_on_rails.html.







Also tagged with one or more of these keywords: rails 3.0, rails 3.2, upgrade rails

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users