Newbe Dev Stack

Answer : You just need to change directories to your app, THEN run bundle install :) You may also indicate the path to the gemfile in the same command e.g. BUNDLE_GEMFILE="MyProject/Gemfile.ios" bundle install I had this problem as well on an OSX machine. I discovered that rails was not installed... which surprised me as I thought OSX always came with Rails. To install rails sudo gem install rails to install jekyll I also needed sudo sudo gem install jekyll bundler cd ~/Sites jekyll new <foldername> cd <foldername> OR cd !$ (that is magic ;) bundle install bundle exec jekyll serve Then in your browser just go to http://127.0.0.1:4000/ and it really should be running

Answer : Alternatively, you can also remove bundler 2.x completely and only use Bundler 1.x: gem uninstall bundler -v ">= 2.0" gem install bundler -v "< 2.0" # Now you can use bundler as before bundle install Try to use gem install bundler -v 1.17.3 bundle _1.17.3_ install Your bundler gem is too big. You can downgrade for now by changing your gemfile to specify the lower version, and deleting the lock file again. gem 'bundler', '1.17.1' Then try these commands in the terminal gem install bundler -v 1.17.1 gem uninstall bundler -v 2.0.1 bundle update --bundler bundle install That last install command might be redundant. I'm on my phone so I can't test anything unfortunately. Best of luck! EDIT: This is now a Heroku issue. Got it. Heroku docs regarding Bundler Libraries The following libraries are used by the platform for managing and running >Ruby applications and cannot be specified. For application dependenc...

Answer : Open the Gemfile and change first line from this source 'https://www.rubygems.org' to this source 'http://www.rubygems.org' remove the ' s ' from ' https '. As @Wasif mentioned, first make sure the Ruby Gems site is up and your network access is ok. If they works fine, try it like this: First, delete your Gemfile.lock file Then run gem update --system Then in your Gemfile try changing the first line source 'https://rubygems.org' to http:// (without an s ) Unless there is a problem with your connectivity this should fix the issue with bundle install .

Answer : It makes little (if any difference). The code using an additional bundle is slightly heavier (it won't make any difference in any practical application) and slightly easier to manage, being more general. If one day you decide that - before sending information inside an intent - you want to serialize the data to database - it will be a bit cleaner to have a bundle that you can serialize, add to an intent and then feed to a PendingBundle - all with one object. [update] A clarification (because of some other answers). Extras is an additional bundle that each Intent might carry (but doesn't have to), so there is no alternative between using a bundle or not using it. You are using a bundle either way. The first time you use putExtra , a mExtras bundle inside Intent is initialized and all the following putExtra are delegated to it. The bundle itself is inaccessible to you (this is by design, to avoid certain kind of bugs). putExtras does not put your bundle...