As a quick addendum, I just tried cap deploy (just for the heck of it)
and got this back, same:

command "sudo  chgrp -R deploy /var/www/apps/mpg/current/tmp /var/www/
apps/mpg/shared" failed on deploy@<server>


On Jun 5, 8:44 pm, joshuajnoble <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'm so close to my first deploy after going through three long nights
> stretched out over a week: I'm running Capistrano 1.4.1 and deprec
> 1.7.1 and I've gotten to the final step (I think):
>
> cap deploy_with_migrations
>
> which is giving me the following error:
>
>  * executing "sudo  chgrp -R deploy /var/www/apps/mpg/current/tmp /var/
> www/apps/mpg/shared"
>     servers: ["deploy@<server>"]
>     [deploy@<server>] executing command
>  ** [out :: deploy@<server>] chgrp: cannot access `/var/www/apps/mpg/
> current/tmp': No such file or directory
>     command finished
> command "sudo  chgrp -R deploy /var/www/apps/mpg/current/tmp /var/www/
> apps/mpg/shared" failed on deploy@<server>
>
> I went and created a file tmp in current and set it's permissions to
> 777 just to make sure it was in fact there and accessible, but no
> love. I'm on slicehost and their tutorials claim that this error
> should be fixed by updating to Deprec > 1.6, but that's not my case.
> Should I be trying something other than "cap deploy_with_migrations"
> or is there a common problem that I might be messing up? Thanks for
> any tips!
>
> Josh


--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---

Reply via email to