similar to: HOW TO REBUILD DATABASE WITH CAPISTRANO

All, Just read in the Capistrano manual about the Capistrano "migrate" task. There it says that: "By default, all this task does is change to the directory of your current release (as indicated by the current symlink), and run rake RAILS_ENV=production migrate. You can specify that it should run against the latest release (regardless of what the current release is) by setting

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

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,

Hi all, I am starting out to play with capistrano. I installed the capistrano gem, and I got some messages. I am not sure if these are errors, warnings or just status messages.I hope someone here can help me understand these messages, so that I don''t suspect Capistrano installation if I run into issues further down. :-) binil$ gem install -r capistrano Attempting remote installation

I''ve created a couple of tasks in my deploy.rb file for starting and stopping backgroundrb on the remote server. The stop task runs fine and kills the process. And the start task *seems* to run successfully, but backgroundrb is never started on the remote host. Has anyone had success with this? Here are my deploy tasks: desc ''Start backgroundrb server (default

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

Hi, has anyone here written a capistrano task for rspec to run through my specs on the deployed server? I''d appreciate a snippet or two to get me started. Thx linoj

Greetings, Today I''ve been working out how to begin using Capistrano and so far I''m impressed. Even in my situation, learning Rails and deploying to a single server, it''s incredibly helpful. I do have one small question though: In using Subversion I''ve used the "ignore" feature to ignore my local database.yml file, because my local database and

Hi all, I''m using Capistrano and SVN to version control and deploy, but I''m not sure what to do about my images directory. I use file_column and RMagick to save images to the disk under a model called "Image", and they''re saved in public/image/... etc. Each time I deploy a new version, my image folder doesn''t exist anymore. I don''t want

I am fighting with this for 5 days... i''m getting crazy! Here is my deploy.rb: require "bundler/capistrano" require "rvm/capistrano" # Load RVM''s capistrano plugin. set :rvm_ruby_string, :local # Or whatever env you want it to run in. ''1.9.3'' set :domain, ''www.xxx.com'' set :application,

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/.

Any idea why this command takes upwards of 15 minutes to complete? run "cd #{release_path} && ORACLE_HOME=/home/oracle RAILS_ENV=production rake db:migrate" When running it against my local Postgres it completes in a few seconds or so. Running it against my local Oracle XE takes only slightly longer. But running it with capistrano over ssh is taking years away from my life.

Hello ~ I am using the Capistrano recipe outlined in this post to restart my backgroundrb server: http://rubyforge.org/pipermail/backgroundrb-devel/2007-February/000718.html My Version: ~~~~~~~~~~~~ task :before_restart, :roles => :app do restart_backgroundrb end task :start_backgroundrb, :roles => :app do sudo "nohup

When trying to start ferret with capistrano, I keep getting this: $ cap services:ferret:stop domain [redken.digitalpulp.com] : user [john] : * executing `services:ferret:stop'' * executing "cd /srv/rails/redken/current; script/ferret_server -e production stop" servers: ["redken.digitalpulp.com"] Password: [redken.digitalpulp.com] executing command ***

Hi. I am using BackgrounDRb to process thumbnails and upload to S3 - things are hunky-dory in development (thumbs are generated, these are uploaded to S3, the metadata is saved to trhe DB, and I get a nice status page updated by periodic calls via ask_status), but when I tried to deploy to our staging server and stop/start BackgrounDRb via Capistrano, things blew up - well, not exactly,

Hi there, The default recipe expects you to be able to access your web server directly from your local machine. On our web server, for security purposes, it is only possible to ssh to it through one particular ip (which is also a remote machine.) The capistrano source is so compact and tidy it looks very hackable. But rather than messing around I thought I''d ask first if anyone else

I am having issues when using unicorn with a Capistrano deployment. >From what I have been able to understand Capistrano uses a scheme in wich every release is deployed inside the releases directory under a unique name and if the transaction was successful, creates a symlink named current that will point to that release. So I end up with a deployment directory such as:

I''m fairly certain this is an easy question to answer but I like to make things more complicated than they need to be. I notice that a lot of people have: RAILS_ENV=production .. in their environment.rb files I don''t have this in mine on production but passenger/apache startup my app just fine in production mode. So, is it really necessary? I also noticed that in order to

When I create a task within capistrano.rb I can call it using rake. When I create a task and put it in deploy.rb I can call it. Neither with or without the remote: namespace. Anyone have any insight into why it does not work? John Kopanas

All, I''m setting up a deployment script with Capistrano at the moment, and am running into some trouble when it attempts to pull the code down from the SVN server when I run the deploy task. The SVN server runs over https, and the problem seems to be when I get asked whether I want to accept or reject the certificate. I hit ''p'' to accept the certificate permanently,