Skip to content
Create a gist now

Instantly share code, notes, and snippets.

Embed URL


Subversion checkout URL

You can clone with
Download ZIP
Suggestions for Metasploit Dev Setup Environment Wiki
##Current Wiki Content
$ curl -L | bash -s stable
$ source ~/.rvm/scripts/rvm
$ rvm install 1.9.3-p125
##Suggestions for Wiki Content
#Set default manually
$ rvm use 1.9.3-p125
$ rvm --default 1.9.3-p125
#Use a gemset so we use 1.9.3-p125 when we drop into msf dir
$ cd ./metasploit-framework
$ rvm use 1.9.3-p125
$ rvm gemset create msf
$ echo "rvm use 1.9.3-p125@msf" > .rvmrc
$ rvm use 1.9.3-p125@msf

ooh good call, thanks! Added.


With more recent versions of rvm (where recently may be over a year, not sure), you can shorten the rvm commands (lines 18-21) to:

rvm use --create --rvmrc 1.9.3-p125@msf

I was once again reminded that I'm not "with the times" on gemset management.

Here's the newer more cross-functional way, although, I'm not a fan of it's invocation, it's definitely more persistent if you need to blow your RVM env away:

echo "gem_set_name" > .ruby-gemset
echo "ruby-2.1.2" > .ruby-version

This of course is done in the root dir of the project.


An even "better" way...

rvm --create --ruby-version use ruby-2.0.0-p247@mycoolapp

Damn kids!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.