Posted over 8 years ago. Visible to the public. Deprecated.

How to upgrade RubyMine

We recommend to use snap to install and update RubyMine:

This card explains how to upgrade an existing RubyMine installation to a newer version. If you're installing RubyMine for the first time, see install RubyMine under Ubuntu. You might also consider installing RubyMine with snap, so it can receive automatic updates (also described in the install card).

This procedure ensures that an update does not totally break your IDE, as it allows you to keep both the previous and the new version of RubyMine:

  1. Download the newest version
  2. [Optional] Copy your license key from HelpRegister; you may need it to reactivate the new version
  3. Shut down RubyMine
  4. Extract the downloaded file into your ~/bin/. [1]

    cd ~/bin && tar xzvf ~/Downloads/RubyMine-X.Y.Z.tar.gz
  5. Update your directory symlink [2] to point to the new version:

    ln -nfs ~/bin/RubyMine-X.Y.Z ~/bin/rubymine
  6. Launch RubyMine as usual. The newly extracted version should start up.
  7. If asked, import your settings and registration information from your previous version. Use your previous installation's directory (e.g. ~/bin/RubyMine-X.Y.Z).
  8. Get back to work.


  • If your license key could not be imported automatically (as described above), you need to launch your old RubyMine version and copy the key from HelpRegister.
  • If you are using the mine command to launch RubyMine from a terminal, you may need to update it, too. Go to ToolsCreate Command-line Launcher… and confirm twice.

[1] We recommend using ~/bin to store binaries for your user. Some of us like to place their RubyMine folders there, too. Alternatively, put them all into a directory like ~/bin/rubymines or ~/Applications.

[2] Ideally, you should symlink your current RubyMine installation to a directory like ~/bin/rubymine, and update that link whenever you update RubyMine. This has many benefits:

  • A launcher pointing to ~/bin/rubymine/bin/ runs the recent version. No need to touch it.
  • Using binaries, icons, etc from the link directory avoids updating every spot in your system that might reference to the old version – and you will forget to update some occasionally.
  • If you encounter problems after updating, simply have the link point back to the old release.
Growing Rails Applications in Practice
Check out our new e-book:
Learn to structure large Ruby on Rails codebases with the tools you already know and love.

Owner of this card:

Arne Hartherz
Last edit:
10 months ago
by Emanuel De
About this deck:
We are makandra and do test-driven, agile Ruby on Rails software development.
License for source code
Posted by Arne Hartherz to makandra dev
This website uses cookies to improve usability and analyze traffic.
Accept or learn more