I deployed to a server that didn't have setfacl binary available. But there was no clear indication of failure. Easy enough to fix but should let the person know this didn't happen.
vagrant@localhost:/vagrant$ drush-deploy TARGET=prod drupal:check_permissions
triggering start callbacks for `drupal:check_permissions'
* 2013-01-25 15:42:59 executing `drupal:load_targets'
** Using drush at "drush"
** Loading target prod
** Using default roles web for target "prod"
* 2013-01-25 15:42:59 executing `drupal:check_permissions'
* executing "ps -eo user,comm,pid,ppid | awk '$2 ~ /^apache.*|^httpd$/ && $1 != U && $3 != P {P=$4; U=$1} END { print U }'"
servers: ["example.com"]
* establishing connection to `xforty@example.com' via gateway
[xforty@example.com] executing command
command finished in 267ms
*** Guessing that apache is the www_user, if this is wrong please set www_user manually in config
* executing "! which setfacl &>/dev/null || { setfacl -Rdm u:apache:rwx /srv/project/shared/default/files && setfacl -Rm u:apache:rwx /srv/project/shared/default/files; }"
servers: ["example.com"]
[xforty@example.com] executing command
command finished in 204ms
vagrant@localhost:/vagrant$ echo $?
I deployed to a server that didn't have setfacl binary available. But there was no clear indication of failure. Easy enough to fix but should let the person know this didn't happen.