-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
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
Drupal Shared Hosting Setup and Deploy breaks on set_perms_dir. #51
Comments
All of the files it's trying to change are owned by aaidura and therefore should be settable without using sudo, in this case. Unless, well, the file is not writeable and/or owned by another user, I guess. |
I added this to my Capfile and this worked: namespace :ash do
desc "Set standard permissions for Ash servers"
task :fixperms, :roles => :web, :except => { :no_release => true } do
# chmod the files and directories.
# set_perms_dirs("#{latest_release}")
run "find #{latest_release} -type d -print0 | xargs -0 chmod 755" if remote_dir_exists?(latest_release)
# set_perms_files("#{latest_release}")
run "find #{latest_release} -type f -print0 | xargs -0 chmod 644" if remote_dir_exists?(latest_release)
end
end |
Duplicate of #50 |
This is still not fixed. #50 seems to fix something in setup, this ticket needs some fixes in ash:fixperms. |
Also, it's not a fatal error, but it also tries to do a sudo chmod on the backups/tmp/{release} folder and that does error out. Again, it doesn't halt the whole script, so it's not as important of an issue. |
Trying to setup or deploy to staging, the set_perms_dir command does not work. This error shows up:
The error is thus:
The text was updated successfully, but these errors were encountered: