If a synced folder's owner or group is set in config.yml, use it.

[fabacab]

In some cases, synced folders exhibit permissions issues as described in Drupal VM's documentation. The suggested fix is currently to edit the Vagrantfile in such a way as to add owner and group options to Vagrant's mount operation. This forces end users to maintain a patched Vagrantfile that differs from the one under version control.

This patch addresses the issue by allowing an untracked config.yml file to set these synced folder options, instead. If no options for owner and group are explicitly defined, a default value of vagrant is set so as to conform to the Vagrant default user conventions. As a result, if a user experiences this issue, they can write a config.yml section for synced folders that looks like the following while leaving the Drupal VM core Vagrantfile untouched:

vagrant_synced_folders:
  - local_path: "."
    destination: "/var/www/drupalvm"
    type: ""
    create: true
    owner: "www-data"
    group: "www-data"

With such a stanza in one's config.yml file, the executed Vagrantfile will be the equivalent of a line such as:

config.vm.synced_folder ".", "/var/www/drupalvm", owner: "www-data", group: "www-data", create: true

[oxyc]

Not as clean but you can do this already using the options_override option