...LTS. This involves upgrading to Rails 2.3.18. The instructions below assume you are using Bundler to manage your gem dependencies. If your project isn't using Bundler, you should upgrade...
Make sure that you have a current version of Rubygems and Bundler, otherwise you might run into random errors with dependency resolution. If you use Ruby 1.8.7, we...
When running bundle install --verbose on Bundler versions 1.12+, you might see errors of the form HTTP 403 Forbidden https://username:password@gems.railslts.com/versions These errors are not fatal, Rails LTS...
...should still be installed correctly. This has been tested with all Bundler versions 1.12.x and 1.13.x. Background: Since version 1.12, Bundler includes a performance optimization called "compact gem...
...involves upgrading to the latest official Rails 4.2 release. Make sure that you have Bundler 1.10 or newer by running: gem list | grep bundler This should show you a line...
bundler (1.10.6) If your version is lower than 1.10, you can update Bundler like this: gem install bundler Please note that you need to have a compatible version...
...at the time of writing. If you are using Rails 2.3 LTS with bundler you can also use current RubyGems versions. ActiveRecord Database Your ActiveRecord models should talk to one...
...Rubies might work with Rails LTS, we only test against the versions listed above. Bundler version Make sure that you have Bundler 1.11 or newer by running: gem list | grep...
...involves upgrading to the latest official Rails 3.2 release. Make sure that you have Bundler 1.10 or newer by running: gem list | grep bundler This should show you a line...
bundler (1.10.6) If your version is lower than 1.10, you can update Bundler like this: gem install bundler Please note that you need to have a compatible version...
...LTS. This involves upgrading to the latest official Rails 6.1 release. Installation Open the Bundler configuration file (Gemfile) in your project's root directory and find this line:
...these credentials in your Gemfile, you can either set them in an environment variable BUNDLE_GEMS__RAILSLTS__COM=username:password. use bundle config set gems.railslts.com username:password
...LTS. This involves upgrading to the latest official Rails 5.2 release. Installation Open the Bundler configuration file (Gemfile) in your project's root directory and find this line:
...these credentials in your Gemfile, you can either set them in an environment variable BUNDLE_GEMS__RAILSLTS__COM=username:password. use bundle config set gems.railslts.com username:password
...you can now set bcrypt-ruby to ~> 3.0 in your Gemfile and do a bundle upgrade bcrypt-ruby with Rails complaining. Dec 21st, 2021: Version 3.2.22.26 Improved compatibility with newer...
...with Postgresql up to version 14. Sep 14th, 2021: Version 3.2.22.25 Relaxed requirement for Bundler. It is now possible to use Rails 3.2 LTS with Bundler 2 (given a compatible...
...with Postgresql up to version 14. Sep 14th, 2021: Version 2.3.18.38 Relaxed requirement for Bundler. It is now possible to use Rails 2.3 LTS with Bundler 2 (given a compatible...
...list for new advisories. June 20th, 2013 We are now officially supporting installation without Bundler or Git. June 18th, 2013 Added missing tests that ensure fixes for CVE...
...helpers (CVE-2022-27777); see details. Sep 14th, 2021: Version 4.2.11.21 Relaxed requirement for Bundler. It is now possible to use Rails 4.2 LTS with Bundler 2 (given a compatible...
...and instructions in this card for your LTS version, gems, and Ruby version. Run bundle install. Try to get rails console (or script/console) running without errors. Try to get rails...
...for Rails 2.3 LTS If you haven't already, you need to switch to Bundler. Add gem 'test-unit', '= 1.2.3', require: false to your Gemfile as a top-level gem...
Rails 3.2 LTS, 4.2 LTS, 5.2 LTS Run the following command: bundle show rails This will display the path of the installed rails gem. The path will contain the version...
...number, e.g. 3.2.22.8 below: /home/alice/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/rails-3.2.22.8 ^^^^^^^^ Rails LTS 2.3 Installation with bundler As a customer of a paid plan who has installed Rails LTS with Bundler, run the following:
...compatibility fork of rspec-rails 1.3. If you are using Rails 2.3 LTS with Bundler you can use the fork by updating your Gemfile: gem 'rspec-rails', :git => 'https://github.com/makandra/rspec-rails.git', :branch => '1-3-lts' Now run bundle update rspec-rails...
...for Rails LTS becomes available. Run the following comment within your Rails project directory: bundle update rails After updating, check that your Gemfile.lock contains the expected changes. If booting Rails...
gem 'actionmailer', :require => false # ... gem 'rack', :require => false # <--- add this end Then run bundle update rack. Note on versions We only maintain the newest supported Rack version for each...
gem 'rspec-rails', :git => 'https://github.com/makandra/rspec-rails.git', :branch => '2-14-lts' Now run bundle update rspec-rails...
...twice their former speed. Upgrade workflow overview If you haven't already, switch to bundler and migrate all config.gem lines to your Gemfile. Update to the latest version of Rails...
...your Gemfile (as a top-level gem and not inside the group :test). Run bundle install. Make minimal version upgrades to your gems until all can be installed. See below...
...at the time of writing) if you are using Rails 2.3 LTS with Bundler. With RubyGems 2+, Rails LTS will restrict the following features which are now supplied by bundler...
...your RubyGems version to a modern 2.x version. This requires you to use bundler to manage your gems. Please see our RubyGems guide for additional details. Third-party gems...
Best results in other decks
Calling bundle update GEMNAME will update a lot more gems than you think. E.g. when you do this: bundle update cucumber-rails ... you might think this will only...
...is a dependency of cucumber-rails), which will break all your tests. The fix Bundler >= 1.14 has a --conservative flag. Using the conservative flag allows bundle update GEM to update...
To keep JavaScript sources small, it can sometimes make sense to split your webpack bundles. For example, if your website uses some large JavaScript library – say TinyMCE – which is only...
...up TinyMCE like this (code is somewhat simplified): // TinyMCE as part of the main bundle! import tinymce from 'tinymce/tinymce' // UI import 'tinymce/themes/silver' import 'tinymce/skins/ui/oxide/skin.min.css' // Plugin import 'tinymce/plugins/autoresize' up.compiler('[tinymce]', (element...