From 252d48a7ca434cba3271431fffefc09f2b66176a Mon Sep 17 00:00:00 2001 From: todb-r7 Date: Mon, 8 Apr 2013 08:15:24 -0700 Subject: [PATCH] Updated Setting Up a Metasploit Development Environment (markdown) --- dev/Setting-Up-a-Metasploit-Development-Environment.md | 2 +- dev/_Sidebar.md | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/dev/Setting-Up-a-Metasploit-Development-Environment.md b/dev/Setting-Up-a-Metasploit-Development-Environment.md index 9e2c43f3e0..e67488f7ce 100644 --- a/dev/Setting-Up-a-Metasploit-Development-Environment.md +++ b/dev/Setting-Up-a-Metasploit-Development-Environment.md @@ -226,7 +226,7 @@ In the end, you'll have a prompt that looks like: where the master bit changes depending on what branch you're in. -## Bundle install +

Bundle install

The first time you download Metasploit, you will need to get your Ruby gems lined up. It's as simple as `gem install bundle && bundle install` from your metasploit-framework checkout. It'll look like this: diff --git a/dev/_Sidebar.md b/dev/_Sidebar.md index 92fc16b213..0336c0773f 100644 --- a/dev/_Sidebar.md +++ b/dev/_Sidebar.md @@ -8,6 +8,7 @@ * [Using Git](#git) * [Forking Metasploit](#fork) * [Setting your Prompt](#prompt) +* [The Ruby Gems Bundle](#bundle) * [Keeping in Sync](#sync) * [Pull Requests](#pull) * [Rspec Tests](#rspec)