From 8dd2c71d2671ddc87bfdf18ebb35a4ca382e59f6 Mon Sep 17 00:00:00 2001 From: Vijay Dev Date: Sat, 29 Dec 2012 00:07:02 +0530 Subject: Revert "reminder to run bundle after setting up rails-dev-box" This reverts commit 41381c19d1f3920ee9540aff0d35209cb43fb057. Reason: This doesn't quite fit the flow where it's added. Let's add this someplace else if it's explicitly required. [ci skip] --- guides/source/contributing_to_ruby_on_rails.md | 7 ------- 1 file changed, 7 deletions(-) (limited to 'guides/source') diff --git a/guides/source/contributing_to_ruby_on_rails.md b/guides/source/contributing_to_ruby_on_rails.md index 59c200fe0c..ce2a5a4902 100644 --- a/guides/source/contributing_to_ruby_on_rails.md +++ b/guides/source/contributing_to_ruby_on_rails.md @@ -49,13 +49,6 @@ To move on from submitting bugs to helping resolve existing issues or contributi The easiest and recommended way to get a development environment ready to hack is to use the [Rails development box](https://github.com/rails/rails-dev-box). -After you have setup your Rails development box and cloned your Rails fork on the host computer, don't forget to run Bundler before you start testing. - - host $ vagrant ssh - Welcome to Ubuntu 12.04 LTS... - ... - vagrant@rails-dev-box:~$ cd /vagrant/rails && bundle install - ### The Hard Way In case you can't use the Rails development box, see section above, check [this other guide](development_dependencies_install.html). -- cgit v1.2.3