vagrant-bindfs 0.2.1 → 0.2.2

Sign up to get free protection for your applications and to get access to all the features.
data/LICENSE.txt CHANGED
@@ -1,6 +1,6 @@
1
1
  The MIT License
2
2
 
3
- Copyright (c) 2010-2012 Folken Laëneck
3
+ Copyright (c) 2010-2013 Gaël-Ian Havard
4
4
 
5
5
  Permission is hereby granted, free of charge, to any person obtaining
6
6
  a copy of this software and associated documentation files (the
data/README.md CHANGED
@@ -3,18 +3,41 @@
3
3
  A Vagrant plugin to automate [bindfs](http://code.google.com/p/bindfs/) mount in the VM.
4
4
  This allow you to change owner, group and permissions on files and, for example, work around NFS share permissions issues.
5
5
 
6
+ ## Some Background: Why `vagrant-bindfs`
7
+
8
+ The default vagrant provider is [virtualbox](https://www.virtualbox.org/).
9
+ It's free, and it works well, but it has some [performance problems](http://snippets.aktagon.com/snippets/609-Slow-IO-performance-with-Vagrant-and-VirtualBox-).
10
+
11
+ People often recommend switching to [vagrant's VMWare-fusion provider](http://www.vagrantup.com/vmware).
12
+ This reportedly has better performance, but shares with symlinks [won't work](http://communities.vmware.com/thread/428199?start=0&tstart=0)
13
+ You also have to buy both the plugin and VMWare-fusion.
14
+
15
+ The final recommendation, at least on Linux/OSX hosts, is to [use nfs](http://docs.vagrantup.com/v2/synced-folders/nfs.html).
16
+ However, an NFS mount has the same numeric permissions in the guest as in the host.
17
+ If you're on OSX, for instance, a folder owned by the default OSX user will appear to be [owned by `501:20`](https://groups.google.com/forum/?fromgroups#!topic/vagrant-up/qXXJ-AQuKQM) in the guest.
18
+
19
+ This is where `vagrant-bindfs` comes in!
20
+ Simply:
21
+
22
+ - mount your share over NFS into a temporary location in the guest
23
+ - re-mount the share to the actual destination with `vagrant-bindfs`, setting the correct permissions
6
24
 
7
25
  ## Installation
8
26
 
9
27
  Vagrant-bindfs is distributed as a Ruby gem.
10
28
  You can install it as any other Vagrant plugin with `vagrant plugin install vagrant-bindfs`.
11
29
 
30
+ ## Usage
12
31
 
13
- ## Configure your VM
32
+ In your `Vagrantfile`, use `config.bindfs.bind_folder` to configure folders that will be binded on VM startup.
33
+ The format is:
34
+ ```ruby
35
+ config.bindfs.bind_folder "/path/to/source", "/path/to/destination", options
36
+ ```
14
37
 
15
- In your VagrantFile, you can use `config.bindfs.bind_folder` to configure folders that will be binded on VM startup.
38
+ ### Example
16
39
 
17
- # In your Vagrantfile
40
+ ```ruby
18
41
  Vagrant::Config.run do |config|
19
42
 
20
43
  [...] # Your VM configuration
@@ -31,8 +54,11 @@ In your VagrantFile, you can use `config.bindfs.bind_folder` to configure folder
31
54
  config.bindfs.bind_folder "/vagrant-nfs", "guest/mount/point"
32
55
 
33
56
  end
57
+ ```
58
+
59
+ ### Supported options
34
60
 
35
- bind_folder support following arguments...
61
+ `bind_folder` supports the following arguments:
36
62
 
37
63
  - `:user` (defaults to 'vagrant')
38
64
  - `:group` (defaults to 'vagrant')
@@ -63,11 +89,27 @@ bind_folder support following arguments...
63
89
  - `:'xattr-rw'`
64
90
  - `:'ctime-from-mtime'`
65
91
 
66
- Ex: ``.
67
-
68
92
  You can overwrite default options _via_ `config.bindfs.default_options`.
69
93
 
70
94
  See [bindfs man page](http://www.cs.helsinki.fi/u/partel/bindfs_docs/bindfs.1.html) for details.
71
95
 
72
96
  vagrant-bindfs does not check compatibility between given arguments but warn you when a binding command fail or if bindfs is not installed on your virtual machine.
73
97
  On Debian systems, it will try to install bindfs automatically.
98
+
99
+ ## Contributing
100
+
101
+ If you find this plugin useful, we could use a few enhancements!
102
+ In particular, capabilities files for installing vagrant-bindfs on systems other than Debian would be useful.
103
+ We could also use some specs...
104
+
105
+ ### How to Test Changes
106
+
107
+ If you've made changes to this plugin, you can easily test it locally in vagrant.
108
+ From the root of the repo, do:
109
+
110
+ - `bundle install`
111
+ - `rake build`
112
+ - `bundle exec vagrant up`
113
+
114
+ This will spin up a default Debian VM and try to bindfs-mount some shares in it.
115
+ Feel free to modify the included `Vagrantfile` to add additional test cases.
@@ -1,3 +1,3 @@
1
1
  module VagrantBindfs
2
- VERSION = "0.2.1"
2
+ VERSION = "0.2.2"
3
3
  end
metadata CHANGED
@@ -2,21 +2,21 @@
2
2
  name: vagrant-bindfs
3
3
  version: !ruby/object:Gem::Version
4
4
  prerelease:
5
- version: 0.2.1
5
+ version: 0.2.2
6
6
  platform: ruby
7
7
  authors:
8
- - "Folken La\xC3\xABneck"
8
+ - "Ga\xC3\xABl-Ian Havard"
9
9
  - Igor Serebryany
10
10
  autorequire:
11
11
  bindir: bin
12
12
  cert_chain: []
13
13
 
14
- date: 2013-06-04 00:00:00 Z
14
+ date: 2013-07-22 00:00:00 Z
15
15
  dependencies: []
16
16
 
17
17
  description: A Vagrant plugin to automate bindfs mount in the VM. This allow you to change owner, group and permissions on files and, for example, work around NFS share permissions issues.
18
18
  email:
19
- - folken.laeneck@gmail.com
19
+ - gaelian.havard@gmail.com
20
20
  - igor.serebryany@airbnb.com
21
21
  executables: []
22
22
 
@@ -36,7 +36,7 @@ files:
36
36
  - locales/en.yml
37
37
  - README.md
38
38
  - LICENSE.txt
39
- homepage: https://github.com/folken-laeneck/vagrant-bindfs
39
+ homepage: https://github.com/gael-ian/vagrant-bindfs
40
40
  licenses: []
41
41
 
42
42
  post_install_message: