When I use puphpet, I also need to add lines to config

[superromeo]

I use puphpet.

1. If I don't add config lines to Vagrantfile, my shared folders owned by 'root'.

2. I think add config lines to Vagrantfile when using puphpet it is overkill. But if do so, folder owned by 'vagrant' (ok), but when I do 'composer update' I have:

 Update failed (Failed to execute git remote set-url composer 'https://git.drupal.org/project/commerce' && git rev-parse --quiet --verify '826a443e1496f8c9e15c50505efd574c3d6fee6b^{commit}' || (git fetch composer && git fetch --tags composer)

fatal: error when closing sha1 file: Permission denied
fatal: unpack-objects failed
)

with sudo all is ok.

I've use vagrant-winnfsd before and this command was executed ok.

[Toilal]

winnfsd use 0777 filemode, but nfs4j-daemon emulates POSIX file permission by default, so you may fall into permission issues.

I don't think adding configuration lines to Vagrantfile is overkill. Maybe the default owner should be 1000 though ? Could you paste the configuration that makes things work in your use case ?

[Toilal]

There's also an no so easy to fix issue that sometimes occurs with git and in other use cases, see inetum-orleans/nfs4j-daemon#7.

As a workaround, I use this configuration to use simple permission type in any .git subdirectory

config.nfs4j.shares_config = {:permissions => {:uid => 1000, :gid => 1000}, :globPermissions => {"**/.git{/**,}" => {:type => 'SIMPLE'}}}

[superromeo]

config.yaml.txt
Here is my config.yaml. It is same for winnfsd and nfs4j-daemon.

[Toilal]

I see. What' you mean is that you can't setup Vagrantfile setting from puphpet configuration ?