Updating to rails 2 2 2

Application configuration should go into files in config/initializers all files in that directory are automatically loaded. If you have any custom stuff in – just move it to initializers. Thanks to some files that are in tmp/ you can disable/enable some features to test them in the dev mode, without having to switch to production mode (for example caching).

# Use an evented file watcher to asynchronously detect changes in source code, # routes, locales, etc. # config.file_watcher = Active Support:: Evented File Update Checker New initializer configuration for application controller renderer.

This is a really good feature that finally allows to drop some “bypass like” solutions.

If you didn’t render outside of controllers scope, you can leave this commented. Handle Cross-Origin Resource Sharing (CORS) in order to accept cross-origin AJAX requests.

In this article, I’ll try to cover all the issues that I had, when I was upgrading one of my Rails app from Ruby on Rails 4.2 to Ruby on Rails 5.0.

Note: This is not a complete, covering every possible case tutorial. If so, feel free to comment and I will try to update the post with other issues and solutions. If you don’t have a good code coverage level and you lack tests, upgrading from Rails 4.2 to Rails 5 might be a big problem.



After updating your Gemfile you can do a allow it to overwrite your files and then just add the stuff that was gone (git diff).

IMHO it is way less complex approach, that trying to add all new config options manually.



Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>