haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Replaces Bundler details with Wiki link

This commit is contained in:
Rob Eden 2016-05-04 14:08:35 -04:00
parent eed574b311
commit b1e8506ab0
1 changed files with 3 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
website/source/docs/plugins/development-basics.html.md
View File

@ -67,20 +67,9 @@ your plugin works with another plugin.
With this structure in place, your workflow should be like any other With this structure in place, your workflow should be like any other
Ruby project, with one exception. Because Vagrant uses the internal Ruby project, with one exception. Because Vagrant uses the internal
APIs of Bundler, the version of Bundler used for Vagrant development APIs of Bundler, see [Installing Vagrant from Source](https://github.com/mitchellh/vagrant/wiki/Installing-Vagrant-from-Source)
is pinned to a specific range defined in the for tips for using the correct version of Bundler to install
[vagrant.gemspec](https://github.com/mitchellh/vagrant/blob/master/vagrant.gemspec) dependencies.
file. If the upper bound version is `1.10.6`, then install the
required version of Bundler and Vagrant dependencies with the
following commands:
```
gem install bundler --version '1.10.6' && \
bundle _1.10.6_ install
```
*Be sure to check [vagrant.gemspec](https://github.com/mitchellh/vagrant/blob/master/vagrant.gemspec)
and use the upper bound version of Bundler*
When you want to manually test your plugin, use When you want to manually test your plugin, use
`bundle exec vagrant` in order to run Vagrant with your plugin `bundle exec vagrant` in order to run Vagrant with your plugin