fsevents_to_vm 1.1.1 → 1.1.2
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/CHANGELOG.md +5 -0
- data/README.md +1 -1
- data/lib/fsevents_to_vm/ssh_emit.rb +1 -0
- data/lib/fsevents_to_vm/version.rb +1 -1
- metadata +3 -2
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 9004e604baa1ee22887c5127ae760d4ca27316c5
|
4
|
+
data.tar.gz: 5488f82dcf07a739d02adef71d6d0575051da762
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 679aaeb684a0cd69cbb2641bf82f81d4338f718d3f2871d4d34ebe727df59a8dadfd58d43da3e4d5c8302f9c22987a8ebf9ee4682914daf5ce934c3a10d31616
|
7
|
+
data.tar.gz: 88ebec665cbee427ed082353fe227142c4484969b7f7f442a0ab37db389eff6f8b5e448331a0ea802d7292142a5ae1a7b5f7cd2dd3e69fd7b21b4617c1252e18
|
data/CHANGELOG.md
CHANGED
data/README.md
CHANGED
@@ -34,7 +34,7 @@ First, make sure that `fsevents` isn't already running due to `dinghy start`, ki
|
|
34
34
|
|
35
35
|
Then run manually:
|
36
36
|
|
37
|
-
|
37
|
+
bundle exec ruby exe/fsevents_to_vm start --debug --ssh-identity-file ~/.docker/machine/machines/dinghy/id_rsa --ssh-ip $(dinghy ip) ~
|
38
38
|
|
39
39
|
You can use inotifywait in the VM to watch for events:
|
40
40
|
|
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: fsevents_to_vm
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 1.1.
|
4
|
+
version: 1.1.2
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Brian Palmer
|
8
8
|
autorequire:
|
9
9
|
bindir: exe
|
10
10
|
cert_chain: []
|
11
|
-
date: 2016-
|
11
|
+
date: 2016-05-11 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: rb-fsevent
|
@@ -132,3 +132,4 @@ signing_key:
|
|
132
132
|
specification_version: 4
|
133
133
|
summary: forward OS X file system events to a VM, designed for use with Dinghy
|
134
134
|
test_files: []
|
135
|
+
has_rdoc:
|