search for: deploy_with_migr

I have installed the exception_notification plugin, and it works fine when system is deployed to production. and I have not problems deploying to dev, and not test environments. However, when I try to do a deploy_with_migrations, I get the uninitialized constant ApplicationController::ExceptionNotifiable error. There must be something ''special'' about the test env, but I haven''t seen anything to tell me to set env any differently. I really don''t want notifications in test, but don&...

My app is set up without database.yml in version control. I created a shared_path/config dir, and put database.yml in it. After I update the code, I want to link the app''s database.yml file to the shared config. So I added this task desc ''Copy the database config'' task :after_update_code, :roles => :app do run "ln -s #{shared_path}/config/database.yml

I''ve deployed an application using Capistrano. But on my local machine I edited one of the earlier migrations. I''ve tried "cap deploy_with_migrations", but it looks like it didn''t rebuild the database. How can I do the equivalent of this using Capistrano? "rake db:migrate VERSION=0" "rake db:migrate" -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You rece...

My deployment requires a few extra steps after ''update_code'' and then again after ''symlink''. Until I migrated to capistrano2, I had my own deploy_with_migration task which added these steps. What would be a recommended approach to accomplish the same using capistrano2? Thanks, Helzer --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group....

Hello, Can someone explain me why Capistrano deploys rails code to both :web and :db roles, not only to :app role, which is the only role that actually needs this code. In my setup I do not want to give any SSH access to :db servers other than server management, which is done outside Capistrano. So why Capistrano migrate task needs this access while it could to it from :app server, which

The recent Rails security issue highlighted a concern I''ve had about Rails deploys; namely, you shouldn''t deploy anything to production that you don''t need there. Rails apps have a number of scripts--potential security holes or DOS targets in this case--along with all the other application code you need. There''s no reason you should have script/server, console,

All, Does anyone know if Capistrano/Switchtower actually does anything on the database server as part of the "deploy" task? I''m pretty sure that it doesn''t, but thought I would verify. Thanks, Wes -- Posted via http://www.ruby-forum.com/.

...grel & mongrel cluster - rails - mysql These six steps will get your app running on a server: cd /path/to/railsapp deprec --apply-to . --name projectname --domain www.projectname.com # edit config/deploy.rb to put in details of your subversion repository cap install_rails_stack cap setup cap deploy_with_migrations cap restart_apache Planned for future releases: - postfix with virtual hosts and smtp-auth - custom tasks for specific VPS providers - host based firewall setup - support for other OS/distributions/versions Check out my blog for more info. - Mike http://codemode.blogspot.com/2006/11/dep...