06 Mar '12, 12am

No like: bundler's remember when you do typos keeps installing gems to the wrong dir.

A Gemfile.lock is required. To ensure that the same versions of the gems you developed with and tested with are also used in deployments, a Gemfile.lock is required. This is mainly to ensure that you remember to check your Gemfile.lock into version control. The Gemfile.lock must be up to date In development, you can modify your Gemfile(5) and re-run bundle install to conservatively update your Gemfile.lock snapshot. In deployment, your Gemfile.lock should be up-to-date with changes made in your Gemfile(5) . Gems are installed to vendor/bundle not your default system location In development, it's convenient to share the gems used in your application with other applications and other scripts run on the system. In deployment, isolation is a more important default. In addition, the user deploying the application may not have permission to install gems to the system, or the web...

Full article: http://gembundler.com/man/bundle-install.1.html#REMEMBERE...

Tweets

Has Green Failed Because Environmental Donors Have Been Giving to the Wrong Groups?

Has Green Failed Because Environmental Donors H...

treehugger.com 05 Mar '12, 4pm

Floating out under the radar about ten days ago was a new report on philanthropy and the environmental movement, which pur...

Gemfile(5) - A format for describing gem depend...

gembundler.com 06 Mar '12, 5pm

# setup adds gems to Ruby's load path Bundler.setup # defaults to all groups require "bundler/setup" # same as Bundler.set...

Thanks to @rapidee I found and fixed the @caden...

cadence.com 04 Mar '12, 10am

Since I appear to talking to myself I might as well finish this conversation. It appears that OrCAD has claimed the user v...