I found the solution. Insert the line:
require bundler/capistrano
into deploy.rb
On Jan 17, 8:52 am, jsnark s...@monmouth.com wrote:
Could not find net-ssh-2.2.2 in any of the sources
(Bundler::GemNotFound)
$ ls -l vendor/cache/net*
-rw-rw-r-- 1 xxx xxx 27136 2012-01-17 08:44
On 16 ene, 15:54, jsnark s...@monmouth.com wrote:
Oops. Pilot error.
set :bundle_flags, '--local'
did not work.
On Jan 16, 9:43 am, jsnark s...@monmouth.com wrote:
Usually it looks more like:
set :bundle_flags, --deployment --local --without development test
--deployment has several
Could not find net-ssh-2.2.2 in any of the sources
(Bundler::GemNotFound)
$ ls -l vendor/cache/net*
-rw-rw-r-- 1 xxx xxx 27136 2012-01-17 08:44 vendor/cache/net-
scp-1.0.4.gem
-rw-rw-r-- 1 xxx xxx 61440 2012-01-17 08:44 vendor/cache/net-
sftp-2.0.5.gem
-rw-rw-r-- 1 xxx xxx 133120 2012-01-17
On Jan 13, 3:39 pm, Steven F. li...@ruby-forum.com wrote:
Where did you run bundle install --path vendor/cache? On the
development machine, or the server?
I ran the bundle install command on the server after deploying the
application.
Has there been any progress with a work-around?
No.
On 11 ene, 17:09, jsnark s...@monmouth.com wrote:
I am using capistrano v2.9.0 to deploy to a ubuntu server running
apache v2.2.12, passenger v3.0.4, ruby v1.9.2 and rails v3.0.1. When
I deploy a new application, I often get error messages like:
Could not find net-ssh-2.2.2 in any of the
On Jan 16, 9:25 am, Xuan xua...@gmail.com wrote:
If you add '--local' to your 'set :bundle_flags' statement, capistrano
will automatically look into vendor/cache for the gems during the
deploy process without extra work.
They should be previously packaged with bundle package.
Thank you.
Oops. Pilot error.
set :bundle_flags, '--local'
did not work.
On Jan 16, 9:43 am, jsnark s...@monmouth.com wrote:
On Jan 16, 9:25 am, Xuan xua...@gmail.com wrote:
If you add '--local' to your 'set :bundle_flags' statement, capistrano
will automatically look into vendor/cache for the gems
Well, this makes little sense to me, but it is a work-around for this
problem.
Add the following line to your deploy.rb file:
before deploy:assets:precompile, :bundle_install
I've also run (on the server) bundle config path vendor/cache and
placed export BUNDLE_PATH=vendor/cache in the
I am having the same issue(s). It appears that bundle puts the gems into
vendor/cache, but the application (or capistrano during install?) is not
looking for them there. The installation fails, but examining
shared/cached-copy/vendor/cache on the server (deployment destination)
shows the missing
By the way... running bundle install --path vendor/cache on the
development system, then re-deploying did not fix the problem -- the
deploy still failed at the assets compile step.
To get it to deploy I have to shell into the server, cd to
shared/cached-copy and then run bundle pack to install
Correction. I'm actually running rails v3.0.7.
--
You received this message because you are subscribed to the Google Groups Ruby
on Rails: Talk group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to
On Jan 11, 11:55 am, Colin Law clan...@googlemail.com wrote:
Because that is what bundle install is for, to install the appropriate
gems as defined by Gemfile and gemfile.lock.
The one thing I am not sure of is why it did not work when the gems
were already in vendor/cache. How did you get
On 11 January 2012 18:06, jsnark s...@monmouth.com wrote:
On Jan 11, 11:55 am, Colin Law clan...@googlemail.com wrote:
Because that is what bundle install is for, to install the appropriate
gems as defined by Gemfile and gemfile.lock.
The one thing I am not sure of is why it did not work
On Jan 11, 2:52 pm, Colin Law clan...@googlemail.com wrote:
So the question is, what is the difference between
bundle pack
and
bundle install --path vendor/cache
Colin
I found the pack command in Agile Web Development with Rails, fourth
edition on page 235. I stumbled across the install
14 matches
Mail list logo
