What changed with directory permissions?

[Michael Slater]

In earlier versions of capistrano, I had no problems using
deploy:setup to create directories to hold the application, typically
var/www/apps/appname (with shared, releases, and current inside that).

With the current version (2.5), I find that this directory is created
with root as the owner, and as a result the deployment fails. If I use
":use_sudo, false", then the application directory is created as the
deploy user, and everything works, but I have to create the parent
directory (www/apps) manually, because permissions don't allow that to
be created without sudo. In the past, I've not used the ":use_sudo,
false" directive.

Am I missing something or did this used to be simpler? What changed,
and why?

Michael

[Jamis Buck]

Michael,

The change was actually in 2.4. The deploy:setup command began using
sudo, as the :admin_runner user. If your current user has sufficient
privileges to create directories, just set :admin_runner to the user
variable:

set :admin_runner, user

- Jamis

> --~--~---------~--~----~------------~-------~--~----~
> To unsubscribe from this group, send email to capistrano-...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/capistrano
> -~----------~----~----~----~------~----~------~--~---
>