vagrant-git-sync 1.0 → 1.0.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: ccd5f734d9812703be4767dfe3fdb0dc2b8fc304
4
- data.tar.gz: f4c6e08a4ba3aaab3e49db8f114c066adfffe497
3
+ metadata.gz: 0e5443338f8108666f28ca797609c041adb9ce93
4
+ data.tar.gz: aebc412a9658e895f76a26a71e0e969a3020c99b
5
5
  SHA512:
6
- metadata.gz: d7c5a75203cd66dd73b614269c82bb743ac30a84ddb75980adf69d28194a2b3832218d173ed20c23d6c3f87f03552e18d7cd9fe4e66718a749a629182e591287
7
- data.tar.gz: 4dbc43b493deb2375372a452f902dcea0483c5cd3103882d97809d998cbc92fc53867b35d8addb66592a708ec59c7690330c95cc9905939ce21c4e7756ee6648
6
+ metadata.gz: cfc3d1265448131767b76357b391d1a60b8ad1ff46ab19cc192bbfb4a918646b41f1ad4f04b28b4b389b142a69b8f9d6d05e93bac5431f68ac12e8cdb91a4ae1
7
+ data.tar.gz: d48d1027381223ee5301d3b5ec5701b5795dc8ba698eb4f943f0ab963677907c38dcf4637b991de5157f123b5c3989e59b7a43ed4b017d09862404a522b7062a
data/README.md CHANGED
@@ -1,14 +1,14 @@
1
1
  # vagrant-git-sync
2
2
  A Vagrant plugin that allows teams to automatically keep Git-backed environments in sync
3
3
 
4
- Vagrant comes very close to eliminating the "it works on my machine" idiom. One problem in practice can be that this requires team's to actively keep local Git Vagrant repositories tightly in sync. If this does not occur, then development environments can quickly diverge; bringing back the dreaded "It works on my machine."
4
+ Vagrant comes very close to eliminating the "it works on my machine" idiom. One potential problem in practice is that this requires teams to explicitly keep local Git integration branch copies (containing Vagrant configuration) tightly in sync with their remote counterpart. It's an almost trivial detail, but easy to forget in wake of a largely otherwise automated environment. If the goal is to streamline local developer environments, this plugin can potentialy help in making your workflow leaner.
5
5
 
6
- Since Vagrant promotes plug-n-play environments, we can eliminate this manual step by allowing Vagrant to reason about, and sync the Git workspace in an automated fashion.
6
+ We can eliminate this manual step by allowing Vagrant to reason about, and sync the integration branch in an automated fashion.
7
7
 
8
- This requires some precaution:
8
+ This requires some precaution that vagrant-git-sync manages for us:
9
9
 
10
10
  - Is a feature branch being worked on (Are we off master)? Is the index dirty? If so, we probably don't want to update, and introduce surprises to the developer. vagrant-git-sync handles these cases automatically, and tries to not get in the way. Currently a feature branch is detected if the local branch is not "master".
11
- - Do we have an internet connection? Can we connect to the remote? vagrant-git-sync will try to bail out as early as possible if it detects this is the case.
11
+ - Do we have a stable internet connection? Can we reach the remote? vagrant-git-sync will try to bail out as early if it detects a less than steller connection. We don't want the plugin to introduce long pauses in workflow due to connectivity issues.
12
12
 
13
13
 
14
- vagrant-git-sync injects middleware very early on in the Vagrant lifecycle. This allows us to update any Vagrant configuration (Vagrantfile, Puppet, Chef, etc) before configuration is actually loaded by Vagrant.
14
+ vagrant-git-sync works by injecting middleware very early on in the Vagrant lifecycle. This allows us to update any Vagrant configuration (Vagrantfile, Puppet, Chef, etc) before configuration is actually loaded by Vagrant.
@@ -16,6 +16,7 @@ module VagrantGitSyncModule
16
16
  ui = env[:env].ui
17
17
  if workspace.unsupported_workspace
18
18
  ui.error 'vagrant-git-sync plugin has detected an unsupported workspace in Vagrant working directory. Make sure you have Git installed, with Git managing your Vagrant workspace'
19
+ return
19
20
  end
20
21
  ui.output 'Checking environment..'
21
22
  unless workspace.is_master?
@@ -1,7 +1,7 @@
1
1
 
2
2
  Gem::Specification.new do |spec|
3
3
  spec.name = 'vagrant-git-sync'
4
- spec.version = '1.0'
4
+ spec.version = '1.0.1'
5
5
  spec.authors = ['Jeff Bornemann']
6
6
  spec.email = ['bornemannjs@gmail.com']
7
7
 
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: vagrant-git-sync
3
3
  version: !ruby/object:Gem::Version
4
- version: '1.0'
4
+ version: 1.0.1
5
5
  platform: ruby
6
6
  authors:
7
7
  - Jeff Bornemann
8
8
  autorequire:
9
9
  bindir: exe
10
10
  cert_chain: []
11
- date: 2016-07-13 00:00:00.000000000 Z
11
+ date: 2016-07-14 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: bundler