Created
April 1, 2014 21:16
-
-
Save maxlinc/9923389 to your computer and use it in GitHub Desktop.
Using vagrant-rackspace and vagrant-aws together
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # If you just do: | |
| # $ vagrant plugin install vagrant-aws | |
| # $ vagrant plugin install vagrant-rackspace | |
| # $ vagrant plugin list | |
| # Then it will downgrade vagrant-aws to 0.0.1 (rather than downgrading fog) | |
| # A sample Gemfile | |
| source "https://rubygems.org" | |
| group :plugins do | |
| # If you don't include vagrant in the gem, then when you run `bundle exec vagrant plugin list` you will get the erro: | |
| # > vagrant is not part of the bundle. Add it to Gemfile. (Gem::LoadError) | |
| gem 'vagrant' | |
| # But by adding it to the Gemfile, when you install you will get a message that says: | |
| # > Thanks for wanting to use Vagrant! Unfortunately, this is not the way | |
| # > to install Vagrant anymore. | |
| # Also, when you try to use vagrant outside the bundle again (e.g. in a different project where you don't need any plugins), | |
| # then it may still find the vagrant executable from the gem rather than the system vagrant, so you will get the same message | |
| # from above and vagrant will exit (because it finds, e.g. /opt/boxen/rbenv/shims/vagrant instead of /usr/bin/vagrant | |
| gem 'vagrant-aws', '0.4.1' | |
| gem 'vagrant-rackspace' | |
| end |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment