Module directories installed by custom.sh don't have correct permissions

[mjordan]

custom.sh runs "privileged" (the default), and since it runs as the last provisioner script, any modules or libraries installed in it do not receive the permissions change added in 63a78f9 (and since custom.sh is privileged, the directoreis are owned by root). Two possible fixes: 1) document that any custom.sh that installs modules or libraries needs to run the following after it installs them:

sudo chown -hR vagrant:www-data "$DRUPAL_HOME"/sites/all/modules
sudo chmod -R 755 "$DRUPAL_HOME"/sites/all/libraries
sudo chmod -R 755 "$DRUPAL_HOME"/sites/all/modules

or 2) those permissions commands get moved into an inline shell provisioner (or additional external script) that gets run after custom.sh, or maybe within the if File.exist? block that runs custom.sh if it exists. There may be other more preferable fixes.

[ruebot]

I'd go with option 1. We could document it in the README, and that should resolved it.

[ruebot]

@mjordan would it be worth moving the call out to custom.sh up to right before post.sh? I think that would resolve this issue, and would be better than documenting. If so, I can take care of this.

[mjordan]

👍