vagrant-fsnotify 0.3.0 → 0.3.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: 23df182466bd34328e19486f3cd9aa335fc4e197
-  data.tar.gz: e73a0a426e991d23203c50e80ee27b55f0e1b6bc
+SHA256:
+  metadata.gz: afd5d14e23b69bcb7bea32dfa01294ffac09fc37b2fb16d94e3afad4a06306c2
+  data.tar.gz: b4c61f02e38a5b7af3bf476a8cf3d8fa6e016be34dfcca7490904bc9711f0768
 SHA512:
-  metadata.gz: 7d172404d49d4bbe5e1122eafcaf8673b3910f27963a7c70007a4c5b30800a4e723ebff22efefe0a7726a5807979cc6d8716c5e1fbc3c1611253be5bf77c30f9
-  data.tar.gz: ec440a43f7aae5eba917448215f3469cb4030d959f2b4c4ba5a7d0b5bef3646dc8390a79a3ebccb8fc1ff2a74e93540d685fbcc72bf4158f64e47abe89db6cf0
+  metadata.gz: cf5a30aec9826b8944bdb7bbe75ebfcc83ce6732726a14dfd090d75a679b820974b2c7923388c48a5ee4fa9dbae504020990952515a2164860179bdd03b06f08
+  data.tar.gz: 1f53979826c5233e15310f557d2c309f0edf15a6e64e77b7f3bc7e9439b1d47c995288fc20c0bbfe12eb31b6624db5f65af89e6037ecf19a20cfea63bd8e1e41

data/AUTHORS

@@ -3,3 +3,4 @@
 Adrien Kohlbecker <adrien.kohlbecker@gmail.com>
 Don Morrison <github@elskwid.net>
 Leandro Facchinetti <me@leafac.com>
+Levon Hakobyan <levon.hakobyan@microbiz.com>

data/CHANGELOG.md

@@ -1,3 +1,7 @@
+0.4.0 - 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)

data/Gemfile

@@ -1,7 +1,7 @@
 source 'https://rubygems.org'
 
 group :development do
-  gem "vagrant", git: "https://github.com/mitchellh/vagrant.git", ref: 'v1.7.3'
+  gem "vagrant", git: "https://github.com/hashicorp/vagrant.git", ref: 'v2.2.4'
 end
 
 group :plugins do

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

@@ -92,6 +92,19 @@ $ 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
@@ -145,6 +158,27 @@ folder, add the following to the `Vagrantfile`:
 config.vm.synced_folder ".", "/vagrant", fsnotify: [:added]
 ```
 
+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
 -------------

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

@@ -199,7 +199,7 @@ MESSAGE
       end
 
       tosync.each do |machine, files|
-        machine.communicate.execute("touch -a '#{files.join("' '")}'")
+        machine.communicate.execute("touch -am '#{files.join("' '")}'")
         remove_from_this_machine = files & todelete
         unless remove_from_this_machine.empty?
           machine.communicate.execute("rm -rf '#{remove_from_this_machine.join("' '")}'")

data/lib/vagrant-fsnotify/version.rb

@@ -1,5 +1,5 @@
 module VagrantPlugins
   module Fsnotify
-    VERSION = "0.3.0"
+    VERSION = "0.3.1"
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: vagrant-fsnotify
 version: !ruby/object:Gem::Version
-  version: 0.3.0
+  version: 0.3.1
 platform: ruby
 authors:
 - Adrien Kohlbecker
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2016-04-13 00:00:00.000000000 Z
+date: 2019-04-11 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -80,8 +80,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubyforge_project: 
-rubygems_version: 2.5.2
+rubygems_version: 3.0.3
 signing_key: 
 specification_version: 4
 summary: Forward filesystem change notifications to your Vagrant VM