vagrant-fsnotify 0.0.6 → 0.3.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: 980ee6f0ef0bbb9c668dc07cc8dea559455e3f0d
-  data.tar.gz: 71277c09a929d9ff27e5483d7c1e3b6fbc65130b
+SHA256:
+  metadata.gz: 67c49ed58e768b8d862c56a16758935e722abd51c92f44bcba26affe5a4c8c02
+  data.tar.gz: 1f17acfa20d968e6b9ac1aea5aeedf2a4465859966edc54b1254e6a59d23a378
 SHA512:
-  metadata.gz: 00057f278fd64d3d60244ebb6317c46d31487fc8d725b4b7afafa2001fa1408f9a82b4997799248daf7b9f4a63ba196336ea3d2b728c78a6e6064edd97d7bd9e
-  data.tar.gz: d4400d6134353f3b2a1b0a232a875c214342e3f6728d9ed7787d6756df381994356af7077a744f2532157ab40c1156e0f253b6b442972dcafe389a5a222161e3
+  metadata.gz: 8390dfed9fd75c925da986d2ef422eae14b410f55f720fab93a132231d54453452459b3c124cae077e165a541ec518db4c79b913b814011cef7e4f234de2d513
+  data.tar.gz: 2ca844f611778d2b139f6c792ae2c82f13dd91a5ec07f07d12532e93572c229756519eca82befead5a6b5c70ddb0f51ca0d1389d5b721f827bc052be9802de2f

data/AUTHORS

@@ -0,0 +1,7 @@
+# This file lists all individuals having contributed content to the repository.
+
+Adrien Kohlbecker <adrien.kohlbecker@gmail.com>
+Don Morrison <github@elskwid.net>
+Leandro Facchinetti <me@leafac.com>
+Levon Hakobyan <levon.hakobyan@microbiz.com>
+stice2k <>

data/CHANGELOG.md

@@ -0,0 +1,50 @@
+0.3.2 - 2021-07-12
+==================
+- Add parameter to allow selection of touch flags
+
+0.3.1 - 2019-04-11
+==================
+- Update mtime as well as atime to trigger file events on the guest (#28)
+
+0.3.0 - 2016-04-13
+==================
+- Fix for "No such file or directory" on Windows host (#11)
+
+0.2.0 - 2015-07-14
+==================
+- *Breaking change:* Minimum required Vagrant version changed to 1.7.3+
+- Fixed a dependency issue with celluloid (#10, @leafac)
+
+0.1.1 - 2015-07-05 (yanked)
+===========================
+Note: This release was yanked due to a dependency issue, see #9
+- Added command synopsis (#7, @leafac)
+- Fix issue with vagrant runtime dependency on celluloid (#8, @leafac)
+
+0.1.0 - 2015-07-05 (yanked)
+===========================
+Note: This release was yanked due to a dependency issue, see #9
+- *Breaking change:* Added support for forwading file addition/removal (#6, @leafac)
+- Depend on `vagrant` rather than `listen` for better compatibility with upstream (#5, @leafac)
+- Added documentation (#3 & #4, @leafac)
+
+0.0.6 - 2015-04-16
+==================
+- Fix multimachine use, allow specifying which machine to target (@elskwid)
+
+0.0.5 - 2015-04-11
+==================
+- Fix `listen` dependency
+
+0.0.4 - 2014-08-18
+==================
+- Uses access time modification, rather than modified time
+
+0.0.3 - 2014-08-15
+==================
+- Allow guest path overriding
+
+
+0.0.2 - 2014-08-15
+==================
+- Increase the delay between changes to 2 seconds

data/Gemfile

@@ -1,9 +1,9 @@
 source 'https://rubygems.org'
 
 group :development do
-  gem "vagrant", git: "https://github.com/mitchellh/vagrant.git", ref: 'v1.6.3'
+  gem "vagrant", git: "https://github.com/hashicorp/vagrant.git", ref: 'v2.2.18'
 end
 
 group :plugins do
-  gemspec
+  gem "vagrant-fsnotify", path: "."
 end

data/LICENSE

@@ -1,6 +1,6 @@
 The MIT License (MIT)
 
-Copyright (c) 2015 Adrien Kohlbecker
+Copyright (c) 2015-2019 Adrien Kohlbecker
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

data/README.md

@@ -1,4 +1,214 @@
 vagrant-fsnotify
 ================
 
-Forward filesystem change notifications to your Vagrant VM
+Forward filesystem change notifications to your [Vagrant][vagrant] VM.
+
+Problem
+-------
+
+Some filesystems (e.g. ext4, HFS+) have a feature of event notification.
+Interested applications can subscribe and are notified when filesystem events
+happen (e.g. a file was created, modified or deleted).
+
+Applications can make use of this system to provide features such as auto-reload
+or live updates. For example, [Jekyll][jekyll] regenerates the static website
+and [Guard][guard] triggers a test run or a build when source files are
+modified.
+
+Unfortunately, [Vagrant][vagrant] users have a hard time making use of these
+features when the application is running inside a virtual machine. When the file
+is modified on the host, the event is not propagated to the guest and the
+auto-reload never happens.
+
+There are several bug reports related to this issue:
+
+- <https://www.virtualbox.org/ticket/10660>
+- <https://github.com/guard/listen/issues/53>
+- <https://github.com/guard/listen/issues/57>
+- <https://github.com/guard/guard/issues/269>
+- <https://github.com/mitchellh/vagrant/issues/707>
+
+There are two generally accepted solutions. The first is fall back to long
+polling, the other is to
+[forward the events over TCP][forwarding-file-events-over-tcp]. The problem with
+long polling is that it's painfully slow, especially in shared folders. The
+problem with forwarding events is that it's not a general approach that works
+for any application.
+
+Solution
+--------
+
+`vagrant-fsnotify` proposes a different solution: run a process listening for
+filesystem events on the host and, when a notification is received, access the
+virtual machine guest and `touch` the file in there (or `touch` followed by a
+`rm` in case of file removals), causing an event to be propagated on the guest
+filesystem.
+
+This leverages the speed of using real filesystem events while still being
+general enough to don't require any support from applications.
+
+Caveats
+-------
+
+Due to the nature of filesystem events and the fact that `vagrant-fsnotify` uses
+`touch`, the events are triggerred back on the host a second time.  To avoid
+infinite loops, we add an arbitrary debounce of 2 seconds between `touch`-ing
+the same file. Thus, if a file is modified on the host more than once in 2
+seconds the VM will only see one notification.  If the second trigger on the
+host or this arbitrary debounce is unacceptable for your application,
+`vagrant-fsnotify` might not be for you.
+
+Installation
+------------
+
+`vagrant-fsnotify` is a [Vagrant][vagrant] plugin and can be installed by
+running:
+
+```console
+$ vagrant plugin install vagrant-fsnotify
+```
+
+[Vagrant][vagrant] version 1.7.3 or greater is required.
+
+Usage
+-----
+
+### Basic setup
+
+In `Vagrantfile` synced folder configuration, add the `fsnotify: true`
+option. For example, in order to enable `vagrant-fsnotify` for the the default
+`/vagrant` shared folder, add the following:
+
+```ruby
+config.vm.synced_folder ".", "/vagrant", fsnotify: true
+```
+
+When the guest virtual machine is up, run the following:
+
+```console
+$ vagrant fsnotify
+```
+
+This starts the long running process that captures filesystem events on the host
+and forwards them to the guest virtual machine.
+
+### Run automatically on vagrant up
+
+To have `vagrant fsnotify` start automatically with your guest, you can use triggers. Add this to your `Vagrantfile`:
+
+```ruby
+  config.trigger.after :up do |t|
+    t.name = "vagrant-fsnotify"
+    t.run = { inline: "vagrant fsnotify" }
+  end
+```
+
+Now, whenever you run `vagrant up`, `vagrant fsnotify` will be run as well. Learn more at https://www.vagrantup.com/docs/triggers/
+
+### Multi-VM environments
+
+In multi-VM environments, you can specify the name of the VMs targeted by
+`vagrant-fsnotify` using:
+
+```console
+$ vagrant fsnotify <vm-name-1> <vm-name-2> ...
+```
+
+### Excluding files
+
+To exclude files or directories from being watched, you can add an `:exclude`
+option, which takes an array of strings (matched as a regexp against relative
+paths):
+
+```ruby
+config.vm.synced_folder ".", "/vagrant", fsnotify: true,
+                                         exclude: ["path1", "some/directory"]
+```
+
+This will exclude all files inside the `path1` and `some/directory`. It will
+also exclude files such as `another/directory/path1`
+
+### Guest path override
+
+If your actual path on the VM is not the same as the one in `synced_folder`, for
+example when using [`vagrant-bindfs`][vagrant-bindfs], you can use the
+`:override_guestpath` option:
+
+```ruby
+config.vm.synced_folder ".", "/vagrant", fsnotify: true,
+                                         override_guestpath: "/real/path"
+```
+
+This will forward a notification on `./myfile` to `/real/path/myfile` instead of
+`/vagrant/myfile`.
+
+### Select filesystem events
+
+By default, when the `:fsnotify` key in the `Vagrantfile` is configured with
+`true`, all filesystem events are forwarded to the VM (i.e. file creation,
+modification and removal events). If, instead, you want to select only a few of
+those events to be forwarded (e.g. you don't care about file removals), you can
+use an Array of Symbols among the following options: `:added`, `:modified` and
+`:removed`.
+
+For example, to forward only added files events to the default `/vagrant`
+folder, add the following to the `Vagrantfile`:
+
+```ruby
+config.vm.synced_folder ".", "/vagrant", fsnotify: [:added]
+```
+
+### Set touch flags
+
+By default, the touch command on the VM will be run with modification flag and access flag, setting
+both modification and access attributes of the file. If only either flag should be used the `:touch`
+param can be set per machine config in the `Vagrantfile`. The param supports an array with either or both 
+`:modification` and `:access` values. 
+
+As example, to only set the access attribute of files when they have changed on the host system set the following
+in the `Vagrantfile`:
+
+```ruby
+config.fsnotify.touch = [:access]
+```
+or for instances and providers
+```ruby
+config.vm.define "vm" do |instance|
+    instance.fsnotify.touch = [:access]
+end
+```
+
+Development
+-------------
+
+To hack on `vagrant-fsnotify`, you need a recent ruby and virtualbox installed.
+
+Then, after cloning the repo:
+```shell
+# install development gems
+bundle install
+
+# run vagrant commands by prefixing them with `bundle exec` to run with the plugin installed from source
+# this will launch a basic ubuntu VM and monitor file changes on the current directory
+bundle exec vagrant up
+
+# make changes to the code
+vim lib/vagrant-fsnotify/command-fsnotify.rb
+...
+
+# relaunch the process to activate your changes
+bundle exec vagrant fsnotify
+```
+
+Original work
+-------------
+
+This plugin used [`vagrant-rsync-back`][vagrant-rsync-back] by @smerill and the
+[Vagrant][vagrant] source code as a starting point.
+
+[vagrant]: https://www.vagrantup.com/
+[jekyll]: http://jekyllrb.com/
+[guard]: http://guardgem.org/
+[forwarding-file-events-over-tcp]: https://github.com/guard/listen#forwarding-file-events-over-tcp
+[vagrant-bindfs]: https://github.com/gael-ian/vagrant-bindfs
+[vagrant-rsync-back]: https://github.com/smerrill/vagrant-rsync-back

data/Vagrantfile

@@ -1,122 +1,14 @@
 # -*- mode: ruby -*-
 # vi: set ft=ruby :
 
-# Vagrantfile API/syntax version. Don't touch unless you know what you're doing!
-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"
-
-  # Disable automatic box update checking. If you disable this, then
-  # boxes will only be checked for updates when the user runs
-  # `vagrant box outdated`. This is not recommended.
-  # config.vm.box_check_update = false
-
-  # 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
-
-  # Create a private network, which allows host-only access to the machine
-  # using a specific IP.
-  config.vm.network "private_network", ip: "192.168.33.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.
+Vagrant.configure("2") do |config|
+  config.vm.box = "ubuntu/bionic64"
   config.vm.synced_folder ".", "/vagrant", fsnotify: true
 
-  # 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.provision "shell", inline: "sudo apt-get update && sudo apt-get install -y inotify-tools"
 
-  # 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"
+  config.trigger.after :up do |t|
+    t.name = "vagrant-fsnotify"
+    t.run = { inline: "bundle exec vagrant fsnotify" }
+  end
 end

data/lib/vagrant-fsnotify/command-fsnotify.rb

@@ -4,6 +4,10 @@ module VagrantPlugins::Fsnotify
   class Command < Vagrant.plugin("2", :command)
     include Vagrant::Action::Builtin::MixinSyncedFolders
 
+    def self.synopsis
+      'forwards filesystem events to virtual machine'
+    end
+
     def execute
       @logger = Log4r::Logger.new("vagrant::commands::fsnotify")
 
@@ -29,18 +33,25 @@ module VagrantPlugins::Fsnotify
 
           folder.each do |id, opts|
 
-            next if not opts[:fsnotify]
+            if !(
+                (opts[:fsnotify] == true) ||
+                (
+                  opts[:fsnotify].respond_to?(:include?) &&
+                  (
+                    opts[:fsnotify].include?(:modified) ||
+                    opts[:fsnotify].include?(:added) ||
+                    opts[:fsnotify].include?(:removed)
+                  )
+                )
+              )
+              next
+            end
 
             # Folder info
             hostpath  = opts[:hostpath]
             hostpath  = File.expand_path(hostpath, machine.env.root_path)
             hostpath  = Vagrant::Util::Platform.fs_real_path(hostpath).to_s
 
-            if Vagrant::Util::Platform.windows?
-              # rsync for Windows expects cygwin style paths, always.
-              hostpath = Vagrant::Util::Platform.cygwin_path(hostpath)
-            end
-
             # Make sure the host path ends with a "/" to avoid creating
             # a nested directory...
             if !hostpath.end_with?("/")
@@ -68,7 +79,27 @@ module VagrantPlugins::Fsnotify
       end
 
       if paths.empty?
-        @env.ui.info("Nothing to sync, exiting...")
+        @env.ui.info(<<-MESSAGE)
+Nothing to sync.
+
+Note that the valid values for the `:fsnotify' configuration key on
+`Vagrantfile' are either `true' (which forwards all kinds of filesystem events)
+or an Array containing symbols among the following options: `:modified',
+`:added' and `:removed' (in which case, only the specified filesystem events are
+forwarded).
+
+For example, to forward all filesystem events to the default `/vagrant' folder,
+add the following to the `Vagrantfile':
+
+  config.vm.synced_folder ".", "/vagrant", fsnotify: true
+
+And to forward only added files events to the default `/vagrant' folder, add the
+following to the `Vagrantfile':
+
+  config.vm.synced_folder ".", "/vagrant", fsnotify: [:added]
+
+Exiting...
+MESSAGE
         return 1
       end
 
@@ -95,7 +126,7 @@ module VagrantPlugins::Fsnotify
       Vagrant::Util::Busy.busy(callback) do
         listener.start
         queue.pop
-        listener.stop if listener.listen?
+        listener.stop if listener.state != :stopped
       end
 
       return 0
@@ -113,10 +144,26 @@ module VagrantPlugins::Fsnotify
       end
 
       tosync = {}
+      todelete = []
 
       paths.each do |hostpath, folder|
 
-        modified.each do |file|
+        toanalyze = []
+        if folder[:opts][:fsnotify] == true
+          toanalyze += modified + added + removed
+        else
+          if folder[:opts][:fsnotify].include? :modified
+            toanalyze += modified
+          end
+          if folder[:opts][:fsnotify].include? :added
+            toanalyze += added
+          end
+          if folder[:opts][:fsnotify].include? :removed
+            toanalyze += removed
+          end
+        end
+
+        toanalyze.each do |file|
 
           if file.start_with?(hostpath)
 
@@ -128,7 +175,13 @@ module VagrantPlugins::Fsnotify
             end
 
             @changes[rel_path] = Time.now.to_i
-            folder[:machine].ui.info("fsnotify: Changed: #{rel_path}")
+            if modified.include? file
+              folder[:machine].ui.info("fsnotify: Changed: #{rel_path}")
+            elsif added.include? file
+              folder[:machine].ui.info("fsnotify: Added: #{rel_path}")
+            elsif removed.include? file
+              folder[:machine].ui.info("fsnotify: Removed: #{rel_path}")
+            end
 
             guestpath = folder[:opts][:override_guestpath] || folder[:opts][:guestpath]
             guestpath = File.join(guestpath, rel_path)
@@ -136,6 +189,9 @@ module VagrantPlugins::Fsnotify
             tosync[folder[:machine]] = [] if !tosync.has_key?(folder[:machine])
             tosync[folder[:machine]] << guestpath
 
+            if removed.include? file
+              todelete << guestpath
+            end
           end
 
         end
@@ -143,7 +199,12 @@ module VagrantPlugins::Fsnotify
       end
 
       tosync.each do |machine, files|
-        machine.communicate.execute("touch -a '#{files.join("' '")}'")
+        touch_flags = get_touch_flags(machine.config.fsnotify.touch)
+        machine.communicate.execute("touch -#{touch_flags} '#{files.join("' '")}'")
+        remove_from_this_machine = files & todelete
+        unless remove_from_this_machine.empty?
+          machine.communicate.execute("rm -rf '#{remove_from_this_machine.join("' '")}'")
+        end
       end
 
     rescue => e
@@ -163,5 +224,14 @@ module VagrantPlugins::Fsnotify
 
     end
 
+    def get_touch_flags(touch)
+      if touch.include? :modification and not touch.include? :access
+        return "m"
+      elsif not touch.include? :modification and touch.include? :access
+        return "a"
+      else
+        return "am"
+      end
+    end
   end
 end

data/lib/vagrant-fsnotify/config-fsnotify.rb

@@ -0,0 +1,29 @@
+begin
+  require "vagrant"
+rescue LoadError
+  raise "The vagrant-fsnotify plugin must be run within Vagrant."
+end
+
+if Vagrant::VERSION < "1.7.3"
+  raise <<-ERROR
+The vagrant-fsnotify plugin is only compatible with Vagrant 1.7.3+. If you can't
+upgrade, consider installing an old version of vagrant-fsnotify with:
+  $ vagrant plugin install vagrant-fsnotify --plugin-version 0.0.6.
+ERROR
+end
+
+module VagrantPlugins::Fsnotify
+
+  class Config < Vagrant.plugin("2", :config)
+    attr_accessor :touch
+
+    def initialize
+      @touch = UNSET_VALUE
+    end
+
+    def finalize!
+      @touch = [:modification, :access] if @touch == UNSET_VALUE
+    end
+  end
+
+end

data/lib/vagrant-fsnotify/plugin.rb

@@ -4,8 +4,12 @@ rescue LoadError
   raise "The vagrant-fsnotify plugin must be run within Vagrant."
 end
 
-if Vagrant::VERSION < "1.5"
-  raise "The vagrant-fsnotify plugin is only compatible with Vagrant 1.5+"
+if Vagrant::VERSION < "1.7.3"
+  raise <<-ERROR
+The vagrant-fsnotify plugin is only compatible with Vagrant 1.7.3+. If you can't
+upgrade, consider installing an old version of vagrant-fsnotify with:
+  $ vagrant plugin install vagrant-fsnotify --plugin-version 0.0.6.
+ERROR
 end
 
 module VagrantPlugins::Fsnotify
@@ -18,6 +22,11 @@ module VagrantPlugins::Fsnotify
       Command
     end
 
+    config "fsnotify" do
+      require_relative "config-fsnotify"
+      Config
+    end
+
   end
 
 end

data/lib/vagrant-fsnotify/version.rb

@@ -1,5 +1,5 @@
 module VagrantPlugins
   module Fsnotify
-    VERSION = "0.0.6"
+    VERSION = "0.3.2"
   end
 end

data/vagrant-fsnotify.gemspec

@@ -18,8 +18,6 @@ Gem::Specification.new do |spec|
   spec.executables   = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
   spec.require_paths = ["lib"]
 
-  spec.add_dependency "listen", "2.8.0"
-
-  spec.add_development_dependency "bundler", "~> 1.9"
-  spec.add_development_dependency "rake", "~> 10.0"
+  spec.add_development_dependency "bundler"
+  spec.add_development_dependency "rake"
 end

metadata

@@ -1,57 +1,43 @@
 --- !ruby/object:Gem::Specification
 name: vagrant-fsnotify
 version: !ruby/object:Gem::Version
-  version: 0.0.6
+  version: 0.3.2
 platform: ruby
 authors:
 - Adrien Kohlbecker
-autorequire: 
+autorequire:
 bindir: exe
 cert_chain: []
-date: 2015-04-15 00:00:00.000000000 Z
+date: 2021-08-12 00:00:00.000000000 Z
 dependencies:
-- !ruby/object:Gem::Dependency
-  name: listen
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - '='
-      - !ruby/object:Gem::Version
-        version: 2.8.0
-  type: :runtime
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - '='
-      - !ruby/object:Gem::Version
-        version: 2.8.0
 - !ruby/object:Gem::Dependency
   name: bundler
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ~>
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '1.9'
+        version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ~>
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '1.9'
+        version: '0'
 - !ruby/object:Gem::Dependency
   name: rake
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ~>
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '10.0'
+        version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ~>
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '10.0'
+        version: '0'
 description: Use vagrant-fsnotify to forward filesystem change notifications to your
   Vagrant VM
 email:
@@ -60,7 +46,9 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
-- .gitignore
+- ".gitignore"
+- AUTHORS
+- CHANGELOG.md
 - Gemfile
 - LICENSE
 - README.md
@@ -70,6 +58,7 @@ files:
 - bin/setup
 - lib/vagrant-fsnotify.rb
 - lib/vagrant-fsnotify/command-fsnotify.rb
+- lib/vagrant-fsnotify/config-fsnotify.rb
 - lib/vagrant-fsnotify/plugin.rb
 - lib/vagrant-fsnotify/version.rb
 - vagrant-fsnotify.gemspec
@@ -77,24 +66,23 @@ homepage: https://github.com/adrienkohlbecker/vagrant-fsnotify
 licenses:
 - MIT
 metadata: {}
-post_install_message: 
+post_install_message:
 rdoc_options: []
 require_paths:
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
-  - - '>='
+  - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - '>='
+  - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubyforge_project: 
-rubygems_version: 2.0.14
-signing_key: 
+rubygems_version: 3.1.4
+signing_key:
 specification_version: 4
 summary: Forward filesystem change notifications to your Vagrant VM
 test_files: []