Hi Umair, It didn't seem to work. I did the following from the checked out vagrant-aws directory: bundle install rake build vagrant plugin install pkg/vagrant-aws-0.5.1.gem
Here is what I got back: Vagrant appears to be running in a Bundler environment. Your existing Gemfile will be used. Vagrant will not auto-load any plugins installed with `vagrant plugin`. Vagrant will autoload any plugins in the 'plugins' group in your Gemfile. You can force Vagrant to take over with VAGRANT_FORCE_BUNDLER. You appear to be running Vagrant outside of the official installers. Note that the installers are what ensure that Vagrant has all required dependencies, and Vagrant assumes that these dependencies exist. By running outside of the installer environment, Vagrant may not function properly. To remove this warning, install Vagrant using one of the official packages from vagrantup.com. Installing the 'pkg/vagrant-aws-0.5.1.gem' plugin. This can take a few minutes... Vagrant's built-in bundler management mechanism is disabled because Vagrant is running in an external bundler environment. In these cases, plugin management does not work with Vagrant. To install plugins, use your own Gemfile. To load plugins, either put the plugins in the `plugins` group in your Gemfile or manually require them in a Vagrantfile. On Thursday, October 23, 2014 8:48:51 PM UTC-7, Umair Chagani wrote: > > I think you'll find what you need here: > https://github.com/mitchellh/vagrant/issues/1829 > On Oct 23, 2014 11:43 PM, "Shawn McCarthy" <[email protected] > <javascript:>> wrote: > >> I am pretty new to ruby, so please keep that in mind. I want to try and >> use the latest version of Vagrant from github (as I saw a lot of bug fixes >> the past few days). Here are the steps I took: >> >> From within my ~/git directory: >> 1) git clone https://github.com/mitchellh/vagrant.git >> 2) cd vagrant >> 3) bundle install >> 4) rake install >> >> From within my ~/git directory: >> 1) git clone https://github.com/mitchellh/vagrant-aws.git >> 2) cd vagrant-aws >> 3) bundle install >> 4) rake install >> >> vagrant plugin install vagrant-aws tells me to : To install >> plugins, use your own Gemfile. To load plugins, either put the >> plugins in the `plugins` group in your Gemfile or manually require >> them in a Vagrantfile. >> >> Which Gemfile is it talking about? The one from the vagrant project I >> just checked out above for the vagrant project ? I tried adding the plugin >> I need, vagrant-aws , to that Gemfile like so : >> source "https://rubygems.org"; >> >> gemspec >> >> if File.exist?(File.expand_path("../../vagrant-spec", __FILE__)) >> gem 'vagrant-spec', path: "../vagrant-spec" >> else >> gem 'vagrant-spec', git: "https://github.com/mitchellh/vagrant-spec.git >> " >> end >> >> group :plugins do >> gem "vagrant-aws" >> end >> >> I did the bundle install and rake install again as well. When I went into >> my existing Vagrant project directory and did a vagrant up node-chrome-1 >> --provider=aws , I still get the message : >> The provider 'aws' could not be found, but was requested to back the >> machine 'node-chrome-1'. Please use a provider that exists. >> >> Any help would be appreciated. >> >> Thank you! >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Vagrant" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
