Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cannot load such file -- rubber #568

Open
eliotfowler opened this issue Oct 18, 2015 · 2 comments
Open

cannot load such file -- rubber #568

eliotfowler opened this issue Oct 18, 2015 · 2 comments

Comments

@eliotfowler
Copy link

When following the Quick Start guide, I ran into a couple of bumps.

First, I get the following error after running cap rubber:create_staging:

~/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/bundler-1.10.6/lib/bundler/rubygems_integration.rb:292:in `block in replace_gem': capistrano is not part of the bundle. Add it to Gemfile. (Gem::LoadError)

After adding capistrano-rails (I tried just capistrano too) to the Gemfile, I get the following error:

LoadError: cannot load such file -- rubber
~/Code/Samples/rubbertest/Capfile:14:in `require'
~/Code/Samples/rubbertest/Capfile:14:in `<top (required)>'

Any ideas?

@johannesE
Copy link

I am also getting the LoadError: cannot load such file -- rubber
The Capfile is looking for the dependency rubber, which it cannot find.
Apparently my Gemfile has not been changed during vulcanize.

I should add that I originally created my project with rails composer, which added capistrano to it. During the bundle command, I gave permission to override all files, for whose it prompted me. This should have undone all rails composer magic.

@jeremyrajan
Copy link

I had to add:

gem 'rubber', '~>3.1.0'
gem 'open4'
gem 'gelf'
gem 'graylog2_exceptions', :git => 'git://github.com/wr0ngway/graylog2_exceptions.git'
gem 'graylog2-resque'

and

group :development do
 ...
  gem 'capistrano', "~> 2.15.7"
end

You may have to run bundle or bundle update depending upon gem's present on your machine.

TIP: if you are planning on testing rubber, I would suggest destroying instances

cap rubber:destroy

after you have tested it. Or find a free tier ami

 region: ap-southeast-1
 image_type: t1.micro #free tier
 image_id: ami-a4ca8df6

So that you don't have to pay hefty bills :).

Hope that helps!

Cheers,
Jeremy

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants