Please read for an updated status on RailsCasts:
Learn more or hide this
"bundler will only fetch the metadata for the gems that it needs, and not every gem known to man"
made me laugh :)
The link to Episode 308: Oh My ZSH is wrong. It points to episode 301.
Have a nice day.
Thanks for reporting that issue, I've fixed the link :)
After using --binstubs you can add ./bin directory to shell PATH variable.
@ryanb You must be psychic! With unerring regularity you cover topics I'm trying to get my head around. Only yesterday I was experimenting with groups in the gemfile (for using HIRB, WIRB and Awesome Print in the console). Another great, timely episode. Thanks!
Wow, what an incredibly informative episode. I learned quite a few things - especially about my troubles getting my remote production envronment to play well with bundler. Thanks!
awesome episode, thanks for the info
Great stuff Ryan. Nested forms revision will be great. Use your own Gem.
Hey Ryan - great as usual.
If you are using RVM to manage your Rubies they recommend not using the oh-my-zsh bundler plugin - see zsh integration with RVM.
RVM provides the functionality built in to the .rvmrc file to automatically add the project --binstubs directory to your path when you cd into the project, just follow the RVM Hook instructions on the RVM bundler page. Works automatically and no more bundle exec.
Thank you Ryan.
I read the documents about upgrading bundler but after bundler upgraded to 1.1, the other dependent gems also changing. I don`t know that being any problem occur on existing project after bundler upgrading? How can i upgrade to bundler 1.1 without any problem?
I want to ask a question that how can i upgrade bundler on production system? So i upgrade my bundler without problem from 1.0.10 to 1.1.0 as follows.
# gem install bundler --version='1.1' --no-rdoc -no-ri
# gem uninstall bundler
Select gem to uninstall:
3. All versions
You have requested to uninstall the gem:
jquery-rails-1.0.18 depends on [bundler (~> 1.0.0)]
kaminari-0.10.4 depends on [bundler (>= 1.0.0)]
orm_adapter-0.0.7 depends on [bundler (>= 1.0.0)]
orm_adapter-0.0.5 depends on [bundler (>= 1.0.0)]
rails-3.0.11 depends on [bundler (~> 1.0)]
rails-3.0.7 depends on [bundler (~> 1.0)]
rails-3.0.5 depends on [bundler (~> 1.0)]
thor-0.14.6 depends on [bundler (~> 1.0)]
If you remove this gems, one or more dependencies will not be met.
Continue with Uninstall? [Yn] Y
Successfully uninstalled bundler-1.0.10
# bundle update
# bundle package
thats all and everyting fine for me.
You could have talked about --deployment =(
Awesome info. Thanks Ryan.
It is really so nice. thank you for your share.
As always, your Railscasts are timed just right... just upgraded Bundler before watching this and got the fatal nokogiri build stuffs
For me, I had to do:
bundle config build.nokogiri --with-xml2-include=/usr/local/Cellar/libxml2/2.7.7/include/libxml2 --with-xml2-lib=/usr/local/Cellar/libxml2/2.7.7/lib --with-xslt-dir=/usr/local/Cellar/libxslt/1.1.26 --with-iconv-include=/usr/local/Cellar/libiconv/1.14/include --with-iconv-lib=/usr/local/Cellar/libiconv/1.14/lib
Point is, your Railscast got me in the right direction, but I needed to refer to a similar issue when previously setting up my Macbook Pro at https://gist.github.com/746966#gistcomment-80034
First sign in through GitHub to post a comment.