RVM::FW works really well to make it possible to use RVM (or rbenv even) inside a restrictive LAN or Firewall just like you do at home.
$ git clone git://github.com/stevenhaddox/rvm_fw.git $ bundle install # For Ruby < 1.9.3 RVM::FW runs in production mode only: $ bundle install --without development test
Download Rubiez and packages:
$ bundle exec rake boot:strap # Or, to keep pre-downloaded Rubies and just add to them: $ KEEP=true bundle exe rake boot:strap
Archive your local setup of RVM::FW and import it into your network.
Deploy! RVM::FW is a simple Sinatra application so you can deploy it anywhere you have Ruby or Rack available internally!
How to Use RVM::FW Once It's Deployed
View a demo to see RVM::FW's user views & instructions for how to setup and use RVM internally. Obviously there are no rubies due to file-size / RVM itself existing on the real Internet.
http(s)://<your_host>:<port>/db to get a plain-text file that your users need to copy and paste into:
~/.rvm/user/db. This file overrides the defaults built into RVM's
~/.rvm/config/db and will point it to your RVM::FW instance to download it's rubies.
You can also visit:
http(s)://<your_host>:<port>/known to get a plain-text file that a user can be put into:
~.rvm/config/known. This will provide a more a accurate list of available rubies when a user runs
rvm list known.
Bonus: If you're an rbenv fan but still stuck in a restricted environment you can use RVM::FW as a simple way to host a central location to keep your Ruby source code. Accessing your desired version of Ruby for rbenv is as simple as querying
http(s)://<your_host>:<port>/public/rubies/<ruby_platform>/<ruby_specific_path>. All the Ruby source paths & packages are easily discoverable within the config/rubies.yml file.
Adding More Rubiez
We're looking into rendering the views for db.erb and known.erb dynamically based upon your custom configuration or the default configuration of config/rubies.yml, but until then you have to manually update and maintain the following files:
- customize config/rubies.yml (defaults to: config/rubies.yml.example)
- update views/db.erb
- update views/known.erb
Any rubies that are found in
/public/rubies will be rendered dynamically in the
/rubies route on the site. The MD5 sums will also be calculated dynamically to ensure users can compare original MD5s vs possibly modified RVM::FW MD5s.
I've recently hit an issue when trying to import certain rubies into my corporate environment. The virus scanner fails on several files. I've tried to add these files to a flagged_file list in the config folder and written a bash script that will remove those files and repackage the ruby. All of these files seem Rdoc or test related thus far so the only real con is that the MD5 sum of the file changes, but at least it allows for automated importing of rubies for those who may hit similar issues with either the ClamAV or McAfee Enterprise virus scanners.
To remove these files from your packages be sure to add any files you need to your
config/flagged_files.txt file unless you are only using the default rubies.yml file. Then run:
This process will take a while as it has to extract each ruby / package file, scan for matching flagged files, remove them and then re-compress or restore the original file as needed.
Stylesheets are handled via the gems:
To update bootstrap, update the version of
bootstrap-sass and run
If you modfy the variables (
sass/_boostrap_variables.scss) or the main application styles (
sass/_rvmfw.scss) then be sure to update the generated CSS files with the appropriate environment command:
$ bundle exec compass compile --output-style compressed -e production $ bundle exec compass compile --output-style nested -e development
I Want to Help!
Special thanks to those who've contributed and helped me maintain RVM::FW over the years.