Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p><strong>modifying rvm scripts is not a good idea</strong></p> <p>I was thinking about your question/my answer while trying to sleep... and I couldn't get an eye closed without writing you another answer. Hacking the rvm install script is really not what you should do. Rvm uses curl everywhere (installation, downloading rubies, updating, ...). And you have to download many more things -- for example gems. Replacing every curl-call in every script is not maintainable.</p> <p><strong>proposed solution</strong></p> <p>The good thing about rvm is, that is stores <em>all</em> its data in the <code>~/.rvm</code> directory. Considering this, you can install rvm on a remote computer (or VM), which is <em>as similar as possible</em> (same OS, same OS version, same libraries) to your development computer. Install all the rubies, gemsets and gems you need. Then move the zipped <code>~/.rvm</code> directory to your development computer and unpack it to <code>~/.rvm</code>.</p> <p>Don't forget to do</p> <pre><code>echo "source $HOME/.rvm/scripts/rvm" &gt;&gt; ~/.bash_profile </code></pre> <p>to source rvm while loading your bash.</p> <p>If you ever have to update or install gems or ruby versions, do your business on the remote computer, and copy <code>~/.rvm</code> again.</p> <p><strong>my experience with this setup</strong></p> <p>I use this setup (although it is automated with our CI server) for ¬2 years now for a production environment which is in a similar wicked corporate network. Changing gems/rubies is harder than it should be, but it works without an internet connection.</p> <p>Edit: Added a paragraph about my experience with this setup</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload