Skip to content
Browse files


Added some notes about how whitespace affects (disables) attempts at command, or context mapping.
  • Loading branch information...
1 parent 456106e commit 7ab352495e001e525340ad156d335261ab00fbf0 @leehambley leehambley committed Feb 13, 2014
Showing with 3 additions and 0 deletions.
  1. +3 −0
@@ -73,11 +73,14 @@ server '', roles: [:db, :workers]
desc "Report Uptimes"
task :uptime do
on roles(:all) do |host|
+ execute :any_command, "with args", :here, "and here"
info "Host #{host} (#{host.roles.to_a.join(', ')}):\t#{capture(:uptime)}"
+**Note:** `execute()` has a subtle behaviour. When calling `within './directory' { execute(:bundle, :install) }` for example, the first argument to `execute()` is a *Stringish* with ***no whitespace***, this allows the command to pass through the [SSHKit::CommandMap]( which enables a number of powerful features . When the first argument to `execute()` contains whitespace, for example `within './directory' { execute('bundle install') }` (or when using a heredoc), Capistrano, nor SSHKit can reliably predict how it should be shell escaped, and thus cannot perform any context, or command mapping, that means that the `within(){}` (as well as `with()`, `as()`, etc) have no effect. There have been a few attempts to resolve this, but we don't consider it a bug, although we acknowledge that it might be a little counter intuitive.
## Before / After
Where calling on the same task name, executed in order of inclusion

0 comments on commit 7ab3524

Please sign in to comment.
Something went wrong with that request. Please try again.