vagrant-nfs_guest 0.1.7 → 0.1.8

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 6d1379c8d93def3e1c8415422a423f262b400a4f
-  data.tar.gz: 1fa184114a1c5cc8dec18f4162a17f3264e82828
+  metadata.gz: 198e6a741e26343a7ac6474db914d04870c245f0
+  data.tar.gz: db2f73ebbeaf1aee9410ca613734e37a63141d7b
 SHA512:
-  metadata.gz: 1c5f0fb3684ae66a003883d266db0bfa0b2f8764262a34d78dc9340a38e267ba02e873684b38bd764d12cc8e4332ed6660ca36ccb63f22f814aace9ff998779b
-  data.tar.gz: 5eaf6f74d023258a47e76f2ec58f37bee8fa796837dab2d80d72484b2479f27c55b7ba5a140e3c651371f255b5349de12e540a35f82f31ee8cb04a4e322ac5d8
+  metadata.gz: 57a3c7615a07b2cae4833833ab61e5b3b7d9687657a52a691a10f9041c4874aea2ba6a1f92d47ed63f35236247dac54778a8fe1b2ce748fa287b9215640baefb
+  data.tar.gz: 45b6b20dcfa3f26dd6a9a46a5a51cf23ca2bda38eb3f75eb6cfe9518e6bb8f02d6f44e88996c38fcf49e0240b944b2c915254617595a38ce147e289de36eee75

data/README.md

@@ -61,13 +61,16 @@ We use 'chruby' to allow a virtual ruby environment for developement. The 'bundl
     bundle exec vagrant
 
 You can test your handy work using the ```example_box``` by doing the following:
+
     cd ./example_box/
     bundle exec vagrant up
 
 You can ssh into the test VM using:
+
     bundle exec vagrant ssh
 
 ... and you can clean up with:
+
     bundle exec vagrant destroy
 
     

data/example_box/Vagrantfile

@@ -5,121 +5,22 @@
 VAGRANTFILE_API_VERSION = "2"
 
 Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
-  # All Vagrant configuration is done here. The most common configuration
-  # options are documented and commented below. For a complete reference,
-  # please see the online documentation at vagrantup.com.
 
   # Every Vagrant virtual environment requires a box to build off of.
-  config.vm.box = "ubuntu/trusty64"
-  #config.vm.box = "centos/7"
-  #config.vm.box = "puphpet/centos65-x64"
-
-  # The url from where the 'config.vm.box' box will be fetched if it
-  # doesn't already exist on the user's system.
-  #config.vm.box_url = ""
-
-  # Create a forwarded port mapping which allows access to a specific port
-  # within the machine from a port on the host machine. In the example below,
-  # accessing "localhost:8080" will access port 80 on the guest machine.
-  # config.vm.network "forwarded_port", guest: 80, host: 8080
+  config.vm.box = "ubuntu/trusty64"           # ubuntu
+  #config.vm.box = "centos/7"                 # centos/7
+  #config.vm.box = "nrel/CentOS-6.5-x86_64"   # centos/6.5
 
   # Create a private network, which allows host-only access to the machine
   # using a specific IP.
   config.vm.network "private_network", ip: "192.168.55.10"
 
-  # Create a public network, which generally matched to bridged network.
-  # Bridged networks make the machine appear as another physical device on
-  # your network.
-  # config.vm.network "public_network"
-
-  # If true, then any SSH connections made will enable agent forwarding.
-  # Default value: false
-  # config.ssh.forward_agent = true
-
   # Share an additional folder to the guest VM. The first argument is
   # the path on the host to the actual folder. The second argument is
   # the path on the guest to mount the folder. And the optional third
   # argument is a set of non-required options.
-  # config.vm.synced_folder "../data", "/vagrant_data"
   config.vm.synced_folder '.', '/vagrant', disabled: true
-  config.vm.synced_folder './vagrant_share', '/vagrant', type: 'nfs_guest'
 
-  # Provider-specific configuration so you can fine-tune various
-  # backing providers for Vagrant. These expose provider-specific options.
-  # Example for VirtualBox:
-  #
-  # config.vm.provider "virtualbox" do |vb|
-  #   # Don't boot with headless mode
-  #   vb.gui = true
-  #
-  #   # Use VBoxManage to customize the VM. For example to change memory:
-  #   vb.customize ["modifyvm", :id, "--memory", "1024"]
-  # end
-  #
-  # View the documentation for the provider you're using for more
-  # information on available options.
-
-  # Enable provisioning with CFEngine. CFEngine Community packages are
-  # automatically installed. For example, configure the host as a
-  # policy server and optionally a policy file to run:
-  #
-  # config.vm.provision "cfengine" do |cf|
-  #   cf.am_policy_hub = true
-  #   # cf.run_file = "motd.cf"
-  # end
-  #
-  # You can also configure and bootstrap a client to an existing
-  # policy server:
-  #
-  # config.vm.provision "cfengine" do |cf|
-  #   cf.policy_server_address = "10.0.2.15"
-  # end
-
-  # Enable provisioning with Puppet stand alone.  Puppet manifests
-  # are contained in a directory path relative to this Vagrantfile.
-  # You will need to create the manifests directory and a manifest in
-  # the file default.pp in the manifests_path directory.
-  #
-  # config.vm.provision "puppet" do |puppet|
-  #   puppet.manifests_path = "manifests"
-  #   puppet.manifest_file  = "site.pp"
-  # end
-
-  # Enable provisioning with chef solo, specifying a cookbooks path, roles
-  # path, and data_bags path (all relative to this Vagrantfile), and adding
-  # some recipes and/or roles.
-  #
-  # config.vm.provision "chef_solo" do |chef|
-  #   chef.cookbooks_path = "../my-recipes/cookbooks"
-  #   chef.roles_path = "../my-recipes/roles"
-  #   chef.data_bags_path = "../my-recipes/data_bags"
-  #   chef.add_recipe "mysql"
-  #   chef.add_role "web"
-  #
-  #   # You may also specify custom JSON attributes:
-  #   chef.json = { mysql_password: "foo" }
-  # end
+  config.vm.synced_folder './vagrant_share', '/vagrant', type: 'nfs_guest'
 
-  # Enable provisioning with chef server, specifying the chef server URL,
-  # and the path to the validation key (relative to this Vagrantfile).
-  #
-  # The Opscode Platform uses HTTPS. Substitute your organization for
-  # ORGNAME in the URL and validation key.
-  #
-  # If you have your own Chef Server, use the appropriate URL, which may be
-  # HTTP instead of HTTPS depending on your configuration. Also change the
-  # validation key to validation.pem.
-  #
-  # config.vm.provision "chef_client" do |chef|
-  #   chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME"
-  #   chef.validation_key_path = "ORGNAME-validator.pem"
-  # end
-  #
-  # If you're using the Opscode platform, your validator client is
-  # ORGNAME-validator, replacing ORGNAME with your organization name.
-  #
-  # If you have your own Chef Server, the default validation client name is
-  # chef-validator, unless you changed the configuration.
-  #
-  #   chef.validation_client_name = "ORGNAME-validator"
 end

data/lib/vagrant-nfs_guest/providers/parallels/cap/nfs_settings.rb

@@ -4,8 +4,8 @@ module VagrantPlugins
       module Cap
 
         def self.nfs_settings(machine)
-          host_ip  = @machine.provider.driver.read_shared_interface[:ip]
-          machine_ip = @machine.provider.driver.read_guest_ip
+          host_ip  = machine.provider.driver.read_shared_interface[:ip]
+          machine_ip = machine.provider.driver.read_guest_ip
 
           raise Vagrant::Errors::NFSNoHostonlyNetwork if !host_ip || !machine_ip
 

data/lib/vagrant-nfs_guest/version.rb

@@ -1,5 +1,5 @@
 module VagrantPlugins
   module SyncedFolderNFSGuest
-    VERSION = "0.1.7"
+    VERSION = "0.1.8"
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: vagrant-nfs_guest
 version: !ruby/object:Gem::Version
-  version: 0.1.7
+  version: 0.1.8
 platform: ruby
 authors:
 - Alan Garfield
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-12-02 00:00:00.000000000 Z
+date: 2015-12-21 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler