vagrant-persistent-storage 0.0.41 → 0.0.42

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 8b6fcbe85fbafd11aba10b9ec772ad85bee8dac1
-  data.tar.gz: '08126f0dc8642a2105d981d24d24a58d0b97d629'
+  metadata.gz: 8fea4df76b7cb5b01f9ba4704e8e3fce7ab39670
+  data.tar.gz: 51a041b7a43006744aef7d3a56c797cf49bbd811
 SHA512:
-  metadata.gz: 235109457598007b30d2b37cc99bf6d3abdbda56574adfad07b46883c63d01f9b172a66bd128a6b5388e17077d760303b23ba4288f2be69a84448ee68c791725
-  data.tar.gz: 0d95fe95d921f220916071148eca211bb9b760974576d4fe90555c727575901619f23c359ee902b87e33f32c62ff9382e67788579fbb4d316e3108de2d850789
+  metadata.gz: 6e1f395a5816ff517a0ba44da407263c44029a4e74455fb1bce1524c9d707eea15429fdcae500ceabc8636eb3cbc4257ce0decd7e8c2f900c14e86f7fb693942
+  data.tar.gz: 26db2ae4f77b3b8dec1392f518382ac9e6c4a3d042f2643f0d6aa797cab7440c19f883ebe22a9974619d87575eeb0527e478b83015f76be262a167f60dda8adb

data/README.md

@@ -13,7 +13,7 @@ Requires Virtualbox 5
 After installing you can set the location and size of the persistent storage.
 
 The following options will create a persistent storage with 5000 MB, named mysql,
-mounted on /var/lib/mysql, in a volume group called 'vagrant'
+mounted on /var/lib/mysql, in a volume group called 'myvolgroup'
 ```ruby
 config.persistent_storage.enabled = true
 config.persistent_storage.location = "~/development/sourcehdd.vdi"
@@ -25,7 +25,7 @@ config.persistent_storage.volgroupname = 'myvolgroup'
 ```
 
 With `config.persistent_storage.mountoptions` you can change the mount options (default: defaults).  
-A example which sets `prjquota` option with xfs.
+An example which sets `prjquota` option with xfs.
 ```ruby
 config.persistent_storage.mountname    = 'xfs'
 config.persistent_storage.filesystem   = 'xfs'
@@ -45,7 +45,7 @@ config.persistent_storage.partition = false
 
 Every `vagrant up` will attach this file as hard disk to the guest machine.
 A `vagrant destroy` will detach the storage to avoid deletion of the storage by vagrant.
-A `vagrant destroy` generally destroys all attached drives. See [VBoxMange unregistervm --delete option][vboxmanage_delete].
+A `vagrant destroy` generally destroys all attached drives. See [VBoxManage unregistervm --delete option][vboxmanage_delete].
 
 The disk is initialized and added to it's own volume group as specfied in the config; 
 this defaults to 'vagrant'. An ext4 filesystem is created and the disk mounted appropriately,
@@ -64,7 +64,7 @@ Options that are irrelevent to Windows are ignored, such as `mountname`, `filesy
 
 ## How Is The Storage Created?
 
-Based on the configuration provided, during a `vagrant up` a bash script is generated and uploaded to `/tmp/disk_operations_#{mnt_name}.sh` (Linux) or `disk_operations_#{mnt_name}.ps1` (Windows).  If the box has not been previously provisioned the script is executed on a `vagrant up`.  To force the scrip to be executed again you can run `vagrant provision` or if you have halted the box, `vagrant up --provision`.
+Based on the configuration provided, during a `vagrant up` a bash script is generated and uploaded to `/tmp/disk_operations_#{mnt_name}.sh` (Linux) or `disk_operations_#{mnt_name}.ps1` (Windows).  If the box has not been previously provisioned the script is executed on a `vagrant up`.  To force the script to be executed again you can run `vagrant provision` or if you have halted the box, `vagrant up --provision`.
 
 The outcome of the script being run is placed in the home drive of the vagrant user in a file called `disk_operation_log.txt`.
 
@@ -76,7 +76,7 @@ config.persistent_storage.part_type_code = '82'
 
 ## Troubleshooting
 
-If your box are not using LVM you must set `config.persistent_storage.use_lvm = false`.
+If your box is not using LVM you must set `config.persistent_storage.use_lvm = false`.
 
 ## Supported Providers
 
@@ -105,6 +105,7 @@ If your box are not using LVM you must set `config.persistent_storage.use_lvm =
 * [Philipp Schrader](https://github.com/philsc)
 * [Alex Tomkins](https://github.com/tomkins)
 * [Marcin Wolny](https://github.com/mwolny)
+* [Adam Huffman](https://github.com/verdurin)
 
 ## TODO
 

data/lib/vagrant-persistent-storage/manage_storage.rb

@@ -94,6 +94,7 @@ echo "vg activation returned:  $?" >> disk_operation_log.txt
 MNT_NAME=#{mnt_name}
 [[ `blkid -t LABEL=${MNT_NAME:0:16} | grep #{fs_type}` ]] || mkfs.#{fs_type} -L #{mnt_name} #{device}
 echo "#{fs_type} creation return:  $?" >> disk_operation_log.txt
+<% end %>
 <% if mount == true %>
 # Create mountpoint #{mnt_point}
 [ -d #{mnt_point} ] || mkdir -p #{mnt_point}
@@ -104,7 +105,6 @@ echo "fstab update returned:  $?" >> disk_operation_log.txt
 [[ `mount | grep #{mnt_point}` ]] || mount #{mnt_point}
 echo "#{mnt_point} mounting returned:  $?" >> disk_operation_log.txt
 <% end %>
-<% end %>
 exit $?
         EOF
 		end

data/lib/vagrant-persistent-storage/version.rb

@@ -1,5 +1,5 @@
 module VagrantPlugins
   module PersistentStorage
-    VERSION = "0.0.41"
+    VERSION = "0.0.42"
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: vagrant-persistent-storage
 version: !ruby/object:Gem::Version
-  version: 0.0.41
+  version: 0.0.42
 platform: ruby
 authors:
 - Sebastian Kusnier
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2018-01-01 00:00:00.000000000 Z
+date: 2018-03-26 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rake