Open jrochkind opened 9 years ago
It's not always uglifier, if I wipe out the deploy directory and try again, it can be a different gem each time.
I realized I could try again with: set :bundle_flags, '--deployment --verbose'
Aha, now I see:
Gem::RemoteFetcher::FetchError: Errno::ECONNRESET: Connection reset by peer - SSL_connect (https://rubygems.org/gems/umlaut_borrow_direct-1.0.0.gem)
Okay, I'll have to investigate that. I'm not able to reproduce that in an interactive shell, only via capistrano -- is there anything that might effect gem fetching of an https .gem file differently via cap vs via an interactive shell, that I should look at?
@jrochkind Hey! Did you found a solution?
I'm not sure if this is a capistrano-rvm problem or a capistrano-bundler problem, or what, but I'll try reporting it here, for advice on how to figure out more on what's going on.
I have
require 'capistrano/rvm'
in my Capfile, followed byrequire 'capistrano/rails'
.When I try a cap deploy, it is unable to do the bundle install:
If I log in to an interactive bash shell directly under the same cap
user
, I an do agem install uglifier -v '2.7.1'
no problem.I can also, interactively, even do a
cd /opt/umlaut_jh/releases/20150506173737 && ~/.rvm/bin/rvm default do bundle install --path /opt/umlaut_jh/shared/bundle --without development test --deployment
without a problem. Once I've manually run thatbundle
command, I can subsequently do acap deploy
, because the gems are all there already -- but I expect that I'll have a problem again whenever I have a new gem in a cap deploy, so that's not good.Any ideas of what might be going on, or how I might investigate or debug this further?