...script is relying on. Run it from any project directory like this, passing a Capistrano multistage deployment target: console-for staging This script is part of our geordi gem on...

...are stored per server (unless you choose a centralized logging solution). Here is a Capistrano task that connects to all servers and prints logs to your terminal like this:

...use the LOG env variable, like LOG=sidekiq cap production app:logs. Note that Capistrano truncates lines that are longer than your terminal. This can be painful when looking at...

There is a conflict between current capistrano versions and the 2.5.1 net-ssh gem. Make sure you upgrade to 2.5.2, then it should work again...

github.com

Note: capistrano_colors was merged into Capistrano starting from v2.13.5. However, this requires Ruby 1.9+. If you cannot upgrade Capistrano to 2.13.5+ (e.g. because you're still running on Ruby...

...simply put capistrano_colors into your Gemfile and require 'capistrano_colors' in your config/deploy.rb file...

...proxy env variable, Bundler will also look for a http_proxy env variable. With Capistrano Ideally the server you're deploying on exports an https_proxy variable for all shells...

...t have control over the server setup, you can also add this to your Capistrano config: set :bundle_env_variables, { 'https_proxy' => 'http://myproxy...

...will ask you for the names of your master branch, production branch and production Capistrano stage. Get the new script by saying sudo gem install geordi You can now say...

...the dump to your project's tmp directory and name it according to the capistrano stage you're calling for, here: staging.dump. When you pass the optional -s option, the...

...and run all pending migrations before restarting it, you can use the following standard Capistrano task: cap deploy:migrations Little is known what happens when the deployment goes through, but...

makandracards.com

deploy-to-production now calls Capistrano with bundle exec since we started to bundle Capistrano in all projects...

github.com

If you have different users for different servers, don't use set :user. Encode the username into the server definition...

opensoul.org

Sometimes, you just need to shoot from the hip…or deploy your local changes without committing them. Put this snippet...

makandra dev

Typically this can cause an error while deploying an application with capistrano: could not verify server signature (SSHKit::Runner::ExecuteError) or Ed25519::VerifyError: signature verification failed!

github.com

A collection of useful utilities for Capistrano deployments

In order to bring up a textual description of a Capistrano task you can say cap -e taskname ... where taskname is the name of the task you're not sure...

Running commands on multiple servers at the same time With a custom Capistrano task: CMD='zgrep -P "..." RAILS_ROOT/log/production.log' bundle exec cap production app:run_cmd See Capistrano...

...deployments, you only need to add storage to the linked_dirs in config/deploy.rb For Capistrano 2, add this to your config/deploy.rb: namespace :paperclip do desc "Create a storage folder for...

...before "deploy:setup", 'paperclip:create_storage' after "deploy:update_code", "paperclip:link_storage" For Capistrano 3, add the following (untested) to your config/deploy.rb: namespace :paperclip do desc "Create a storage...

...achieved and how to fix it. Theory When you deploy a new Ruby version with capistrano-opscomplete, it will take care of a few things: The new Ruby version is...

...anyway. Don't do this unless you absolutely need to. There is a taks in capistrano-opscomplete-0.6.4 which can do that for you (see below). In capistrano-opscomplete...

etag { @@revision ||= File.read('REVISION') rescue nil } # Change all ETags after a new Capistrano release. etag { up.target } # Add this when you use Unpoly < 3 and optimize responses for render...

Carrierwave Go through our Carrierwave checklist if used. Maintenance Integrate and test the capistrano maintenance task. Accessibility Decide what effort you want to put in improving accessibility for physically...

github.com

As we get ready to upgrade our servers I thought it’d be a good time to upgrade our deployment...

makandracards.com

...to speed up deployment, asset precompilation can be skipped. This card automates the process. Capistrano 3 namespace :deploy do desc 'Automatically skip asset compile if possible' task :auto_skip_assets...

...and re-use the previous release's assets. [1] That is especially easy via Capistrano. Capistrano will automatically symlink your release's public/assets to a shared directory, so all you...

...deploy:assets:precompile task. Put the following code where you'd put other custom Capistrano tasks (default is lib/capistrano/tasks/*.rake) if ENV['SKIP_ASSETS'] Rake::Task['deploy:assets:precompile'].clear...

...on the next request. http://blog.phusion.nl/2014/01/02/phusion-passenger-4-0-33-released/ If you want to use this with capistrano 2.x just replace the touch command: - run "touch #{current_path}/tmp/restart.txt" + run "passenger-config...

...restart-app --ignore-app-not-running #{deploy_to}" If you are using capistrano 3.x: - execute :touch, "#{current_path}/tmp/restart.txt" + execute "passenger-config restart-app --ignore-app-not-running #{deploy...