God question. You've stumbled across a problem that no-one's reported
in almost three years but it's quite valid.
The quick solution is to add the following to your deploy.rb:
set :deploy_to, "/u/apps/#{application}"
The long answer is that at first, deprec used /var/www/apps because it
was where one might expect to find web apps. This was changed to /opt/
apps/ when deprec started installing the apache package instead of
compiling from source.
Capistrano puts this in generated deploy.rb files when you run
"capify ."
# If you aren't deploying to /u/apps/#{application} on the target
# servers (which is the default), you can specify the actual
location
# via the :deploy_to variable:
# set :deploy_to, "/var/www/#{application}"
Deprec puts this in generated deploy.rb fileswhen you run "depify ."
# If you aren't deploying to /opt/apps/#{application} on the target
# servers (which is the deprec default), you can specify the actual
location
# via the :deploy_to variable:
# set :deploy_to, "/opt/apps/#{application}"
It would have been cleaner to have explicitly set :deploy_to in the
deploy.rb deprec generates
rather than update the value within the library and show where in
deploy.rb it can be reset.
This would avoid the problem you've encountered when deploying using a
non-deprec generated depoy.rb
I'll note that for fixing.
- Mike