vagrant-listen-server 0.0.2 → 0.0.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 2cfeb1cec6dac82766c551f2f274d37e3c0de392
-  data.tar.gz: 834d63a319938c3c5421ec444156b827f510a6d1
+  metadata.gz: d6bc4b1dc74d14a2265d218cfd30d1a65a6d21c3
+  data.tar.gz: 5c2910bca19794cb808df5ba3ec21be5ced9efad
 SHA512:
-  metadata.gz: 17bec5357fa7ea92af00b9954c61c9034ef08d3db310a43524d5f0f789d02c0dee2fe12ce8ad662cb8f405314861dad027f0207ccf5a20eec69c89018c2449b8
-  data.tar.gz: a3c4f81f2255169a77bfc4c139a8052c538cb74664510664114d33d586a3c1021c829ff7e617abe185f169bfcd2ae356c5cfd25d3045061a3961e83b6984ba46
+  metadata.gz: 66746b24cd27bf4d4a003f6dab284e777266c0714738e9ae3a33ec17ff28cbe8f6c97610b36bdcdca517c52aa8b9cbae0af905e249f62ea8bc219cb9a6988740
+  data.tar.gz: 54fb1ba72bba130fce0c253e15e47a78f903d3bc38b0fbde36a92f5e1b231c7e02b8fae7c792bc4f6e625d9ebdd8e8f082a1702f0a6056b1cfba5122b4f4921e

data/.gitignore

@@ -12,3 +12,5 @@
 *.o
 *.a
 mkmf.log
+
+vagrant-listen-server-*.gem

data/README.md

@@ -2,7 +2,6 @@
 
 Forward filesystem events from a host to a client
 
-
 Vagrant's shared folders don't pass file modification notifications to the
 guest. That means editing files locally won't trigger off inotify file events,
 which means any build / test / servers that need to reload on change have to
@@ -15,13 +14,10 @@ are impossible. Statting takes forever.
 Since polling implementations will probably rely on statting the file in some
 way, this creates a pretty awful experience.
 
-
-The answer - forwarding filesystem events
-
-The listen gem is already used by vagrant, (as part of rsync-auto) and allows forwarding of filesystem events over TCP.
-
-# The listen gem, as used by rsync-auto, is apparently a bit of a resource hog
-# because it stats all files before sending events.
+The best answer I've managed to find is forwarding filesystem events. The
+listen gem is already used by vagrant, (as part of rsync-auto) and allows
+forwarding of filesystem events over TCP, so that's what I've tried to stick
+with.
 
 
 ## Clients
@@ -37,7 +33,6 @@ you'll have to be aware of loops created if filesystem notifications are passed
 back from the guest to the host.
 
 
-
 ## Usage
 
 Install the plugin:
@@ -47,29 +42,31 @@ Install the plugin:
 Then in your Vagrantfile:
 
 ```ruby
+  config.vm.synced_folder '/host/code', '/client/code'
+
+  # You have to specify a private network for the guest to connect to.
+  config.vm.network :private_network, ip: '172.16.172.16'
+
   if Vagrant.has_plugin? 'vagrant-listen-server'
-    config.listen_server.ip = '172.168.172.16'
+    # The host will always be the same IP as the private network with the last
+    # octet as .1
+    config.listen_server.ip = '172.168.172.1'
     config.listen_server.port = 4000
-    config.listen_server.folders = '../beyondpricing/client'
-    config.listen_server.pid_file = '/tmp/beyond.listen.pid'
+    config.listen_server.folders = '/host/code'
+    config.listen_server.pid_file = '/tmp/servername.listen.pid'
   end
 ```
 
 
 ## Other options
 
- * rsync-auto
-#   * http://docs.vagrantup.com/v2/cli/rsync-auto.html
-#  Filesystem is shared using rsync-auto protocol instead of vboxsf
-#  Pros: Pushes files onto guest, so guest can fire native events
-#  Cons: Slow, apparently a resource hog.
+ * [rsync-auto](http://docs.vagrantup.com/v2/cli/rsync-auto.html)
+
+Filesystem is shared using rsync-auto protocol instead of vboxsf
 
-     
- * rsync-mirror
-   https://github.com/ingenerator/vagrant-mirror/
-   Looks good, but super outdated.
+ * [rsync-mirror](https://github.com/ingenerator/vagrant-mirror/)
 
-     
+Hasn't been updated to work with vagrant's new plugin system.
 
 
 ## Development
@@ -81,8 +78,9 @@ vagrant plugin install vagrant-listen-server-0.0.1.gem
 ```
 
 Other good vagrant plugins used for reference:
-* https://github.com/mitchellh/vagrant-aws/blob/master/Rakefile
-* vagrant-ls - http://www.noppanit.com/create-simple-vagrant-plugin/
+ * https://github.com/mitchellh/vagrant-aws/blob/master/Rakefile
+ * vagrant-ls - http://www.noppanit.com/create-simple-vagrant-plugin/
+ * vargant-notify - https://github.com/fgrehm/vagrant-notify/blob/master/lib/vagrant-notify/action/start_server.rb
 
 
 ## TODO:

data/lib/vagrant-listen-server/version.rb

@@ -1,5 +1,5 @@
 module VagrantPlugins
   module ListenServer
-    VERSION = '0.0.2'
+    VERSION = '0.0.3'
   end
 end

data/vagrant-listen-server.gemspec

@@ -8,7 +8,7 @@ Gem::Specification.new do |spec|
   spec.version       = VagrantPlugins::ListenServer::VERSION
   spec.authors       = ['David Kelso']
   spec.email         = ['david@kelso.id.au']
-  spec.summary       = %q{Guard / Listen TCP server to publich filesystem events to guests.}
+  spec.summary       = %q{Guard / Listen TCP server to publish filesystem events to guests.}
   spec.homepage      = 'https://github.com/zaius/vagrant-listen-server'
   spec.license       = 'MIT'
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: vagrant-listen-server
 version: !ruby/object:Gem::Version
-  version: 0.0.2
+  version: 0.0.3
 platform: ruby
 authors:
 - David Kelso
@@ -113,5 +113,5 @@ rubyforge_project:
 rubygems_version: 2.2.2
 signing_key: 
 specification_version: 4
-summary: Guard / Listen TCP server to publich filesystem events to guests.
+summary: Guard / Listen TCP server to publish filesystem events to guests.
 test_files: []