Skip to content

Instantly share code, notes, and snippets.

@claudijd
Created May 7, 2012 02:05
Show Gist options
  • Save claudijd/2625441 to your computer and use it in GitHub Desktop.
Save claudijd/2625441 to your computer and use it in GitHub Desktop.
Suggestions for Metasploit Dev Setup Environment Wiki
##Current Wiki Content
$ curl -L get.rvm.io | 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
-OR-
#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
@todb-r7
Copy link

todb-r7 commented May 8, 2012

ooh good call, thanks! Added.

@ckhrysze
Copy link

ckhrysze commented May 9, 2012

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

@claudijd
Copy link
Author

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.

@claudijd
Copy link
Author

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