We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
whoami
I have a hoster where whoami fails, but it is required here:
deployer/recipe/deploy/writable.php
Line 68 in cfcb963
When I set remote_user it is used for the ssh connection as well, but the ssh username is a different name than the one owning the files...
remote_user
Actually, I have set writable_mode to chmod because I expected some kind of problem and the chmod part of this task does not even use $remoteUser.
writable_mode
chmod
$remoteUser
I propose setting $remoteUser in the acl-block:
Lines 101 to 132 in cfcb963
Line 96 in cfcb963
The text was updated successfully, but these errors were encountered:
Fix for deployphp#2850
99e647d
Fix for #2850 (#2852): whoami fails on some hosters
4395362
Successfully merging a pull request may close this issue.
I have a hoster where
whoami
fails, but it is required here:deployer/recipe/deploy/writable.php
Line 68 in cfcb963
When I set
remote_user
it is used for the ssh connection as well, but the ssh username is a different name than the one owning the files...Actually, I have set
writable_mode
tochmod
because I expected some kind of problem and thechmod
part of this task does not even use$remoteUser
.I propose setting
$remoteUser
in the acl-block:deployer/recipe/deploy/writable.php
Lines 101 to 132 in cfcb963
And change the message here to some generic text:
deployer/recipe/deploy/writable.php
Line 96 in cfcb963
The text was updated successfully, but these errors were encountered: