I want to warn: There is a security purpose for using https over http. Try at first the other answers mentioned in this thread. Changing https to http in my Gemfile did the magic. Before I have to create the project with rails new APP –skip-bundle
I also struggled with the same problem. Managed to fix it by setting this parameters in ~/.zshc user profile. You might have different RUBY_PATH, feel free to change it. export RUBY_PATH=/usr/local/opt/ruby/bin export PATH=”$RUBY_PATH:$PATH” export RUBY_VERSION=$($RUBY_PATH/ruby -e “puts RUBY_VERSION”) export PATH=”/usr/local/lib/ruby/gems/$RUBY_VERSION/bin:$PATH” export GEM_HOME=”$HOME/.gem” export GEM_PATH=”$GEM_HOME/ruby/$RUBY_VERSION” You can also take it from this gist
Most people solve this by installing the rails gem first via gem install rails. If you refuse to do that for some reason, you can opt out of the automatic bundling that Rails attempts to do for you. This will work completely regardless of your ruby management system. mkdir myapp cd myapp echo “source :rubygems” … Read more
List configs bundle config Delete value from config bundle config –delete without Add value to config bundle config –local without development Or you can manually edit the values in .bundle/config file.
You need to update Bundler: gem update bundler RubyGems release 2.0 seems to be the trigger for the error: RubyGems 2.0 includes several new features and many breaking changes. Some of these changes will cause existing software to break. . . . If you are using bundler be sure to install a 1.3.0.prerelease version or … Read more
I’d say: by default on your local machine, no particular difference but… The purpose of bundle install is to setup everything for the application containing the Gemfile. You can even pass arguments to make needed gems installed in whatever folder you want. This way in production, you have clearly separated apps with their own gems. … Read more
This is a known issue in Bundler. The workarounds are either: Generate a Gemfile.lock on a system similar enough to your production environment that you get results that match your production platform. Effectively, that means you can only generate the Gemfile.lock file on Windows if your production system is Windows. Don’t commit a Gemfile.lock file … Read more
Im used to have this problem, resolve using bundle –deployment Which will install the gems in vendor/bundle
I was having the same issue. One hint was that rbenv exec bundle exec command worked and that rbenv exec bundle install –path vendor/bundle worked, but their prefixed equivalents failed. I wiped my ~/.rbenv, ~/.gem Gemfile.lock and vendor/bundle a few times trying to start fresh. Once these were cleaned away I tried the following: rbenv … Read more
Answering the second part of your question, developing a plugin/gem and shipping it with the rails app without making the gem publicly available, you may do this Gemfile gem ‘my_private_gem’, :path => “vendor/gems/my_private_gem-VERSION” assuming you performed a gem unpack my_private_gem –target vendor/gems note: bundle package unpacks all gems (as many as in Gemfile.lock). I wouldn’t … Read more