Thanks for the writeup. I've been using bundler for about 6 months (and even have the same 'be' alias!) and understand it, I'm just confused when it seems to magically forget about my installed bundle.
I have run into two reasons why this happens unexpectedly:
1. rvm-related. You installed a gemset for 1.9.2, and then either manually switched to another ruby version, or never set that version as your default. So the next time you come into the project, your ruby version is different and the gemset isn't there.
2. bundler-related: because of other gemsets and your bundler/rvm versions, you need to run commands with the 'bundle exec' prefix (e.g. 'bundle exec rails s') in order to use the context of the current bundle.
The faffing around with RVM gemsets vs Bundler gemsets is why I use rbenv (https://github.com/sstephenson/rbenv), and use Bundler exclusively to manage gemsets per application.
I have a small group of globally-installed gems for convenience when starting new projects (ie. rails).
(I'm lucky enough to not work on anything that doesn't use Bundler, fortunately.)
