>
> I would have expected that commands that are not mapped would have the
> same treatments applied to them as mapped commands. Is there a reason this
> isn't the case? It's not obvious to me.
>
https://github.com/capistrano/capistrano/issues/719#issuecomment-26917090
--
You received this messa
Hi, when I run `rake` to run tests in sshkit, I get an error message that
just says "vagrant", see:
https://gist.github.com/mattconnolly/8213718
I'm not sure how to debug this one, I've never used vagrant before today.
Any tips?
Using:
ruby: ruby 2.0.0p353 (2013-11-22 revision 43784) [x86_64-
Hi,
I have an example using SSHKit:
# ssh-kit-test.rb:
require 'sshkit'
require 'sshkit/dsl'
on 'example.com', user: 'matt' do
within('current') do
puts "this works as expected:"
puts capture :ls
puts "this does not get executed in the 'current' directory:"
puts capture 'ls
I have an example script here: https://gist.github.com/mattconnolly/8212674
I can see in the code that it is bypassing all of the `with`, `within`,
`user` etc conversions when the command has a space in it.
I would have expected that commands that are not mapped would have the same
treatments a
I can't see the words `asset_env` in your Cap3 example? You might try:
with asset_env.merge(rails_env: fetch(:rails_env)) do { }
Assuming asset_env is a hash, in any case with() expects a hash.
Lee Hambley
--
http://lee.hambley.name/
+49 (0) 170 298 5667
On 1 January 2014 05:56, Marvi
In capistrano 2 I could specify this in my deploy.rb and my assets would be
precompiled properly (my app is deployed under a sub-uri)
set :asset_env, "#{asset_env} RAILS_RELATIVE_URL_ROOT=/#{application}"
in capistrano 3 how do I do this? The below does not seem to work... it never
gets pass
