After messing around with deploy.rb I can deploy with this mess of code: namespace :deploy do task :before_finalize_update do switch_to_rails end task :after_finalize_update do switch_back end task :before_migrate do switch_to_rails end task :after_migrate do switch_back end end
namespace :mod_rails do task :before_restart do switch_to_rails end task :after_restart do switch_back end end Am I breaking anything? Deploying a subdir is easy enough with subversion, all you have to do is checkout the rails directory, but this seems much to hard to archive when using git. On May 25, 5:38 pm, Will <[EMAIL PROTECTED]> wrote: > Hi, I am trying to deploy with Capistrano 2.3. Because the rails > directory I am trying to deploy is not in the root of the git repo, > the rake db:migrate fails. How do i tell cap that the rails dir is in > a sub directory? > > set :scm, :git > set :repository, "[EMAIL PROTECTED]:user/repo.git" > set :deploy_via, :remote_cache > set :branch, "origin/development" > > in the origin/development branch the directory structure looks like > this: > > rails/ > another_app/ > another_app2/ > > I have been trying everything I can think of but nothing works. > > Many thanks, > > Will --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
