All mud, no lotus - The Healthy Gemfile

Gemfileの書き方。 / “All mud, no lotus - The Healthy Gemfile”

Often when working on ruby projects that use Bundler , I see Gemfiles that look like this: gem 'rails', '3.0.15' gem 'rest-client', '1.3.0' gem 'subexec', '0.0.4' gem 'uuidtools', '2.1.1' The string on the right hand side of each gem specification is a fixed version specification. If you ask bundler to update any of these gems, it will make a bit of noise but those gems listed will essentially stay the same. The typical reason for structure a Gemfile like this is to prevent changes in dependent software from causing compatibility issues or to reduce the chance of bugs or unexpected behaviour. This strategy is problematic for several reasons: it keeps your project stale, makes it difficult to maintain overall project security and worse yet, can provide a false sense of security. There is a much better and simpler way of writing a Gemfile that will preserve the health and co...

Full article: http://pivotallabs.com/users/jbarker/blog/articles/2286-t...