Josh,
Since cap:deploy:setup can, unless you have disabled it use sudo, it's
entirely possible that your deploy user doesn't have permission to write to
the directories it has setup, there're two options; one check the
permissions on the directories that deploy:setup makes, or alternately, add
something like this to set the permissions to what you were expecting:
after 'deploy:setup' do
run "#{sudo} chmod -R a+rwx {deploy_to}"
# -- or --
run "#{sudo} chown -R {deploy_user} {deploy_to}"
end
I would sincerely suggest you don't blindly assign `a+rwx` unless you'd like
to leave your server's back door open for the bandits, but one or the other
of the above should help you out; if you want a sanity check please paste
the output of a deploy that is causing problems.
- Lee
2009/6/29 Matt Davies <[email protected]>
>
> I had a similar sort of problem but it turned out that I hadn't run
> the cap deploy:setup properly.
>
> Don't ask me how
>
>
>
>
> 2009/6/29 Lee Hambley <[email protected]>:
> > Josh,
> > Did you recently start using git? I suspect the tmp/ directory doesn't
> > exist... Git won't track empty directories.
> > - Lee
> > 2009/6/29 Josh <[email protected]>
> >>
> >> I have never had this problem before, but when I try to do a cap
> >> deploy:update, after a setup and a check that passes, it gives this
> >> error: failed: "sh -c \"touch /home/deployer/apps/staging/current/tmp/
> >> restart.txt\
> >>
> >> This never seemed to be a problem and I have yet to solve it. Any
> >> ideas?
> >>
> >> Thanks.
> >>
> >>
> >
> >
> > >
> >
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Capistrano" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.co.uk/group/capistrano?hl=en
-~----------~----~----~----~------~----~------~--~---
