Changes between Version 2 and Version 3 of RubyOnRailsBundlerGem


Ignore:
Timestamp:
12/10/09 06:59:00 (9 years ago)
Author:
rshaker
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • RubyOnRailsBundlerGem

    v2 v3  
    2828[http://www.kerrybuckley.org/2009/11/02/managing-gems-in-a-rails-project/] 
    2929 
    30 The purpose of this document is to provide instructions for installing and using Bundler to manage an application's. 
     30The purpose of this document is to provide instructions for installing and using Bundler to manage an application's gems. 
    3131Bundler is similar to the unpack and freeze approach. 
    3232 
    33 == Assumptions == 
     33== Assumptions for this discussion == 
    3434 
    3535 * OS version is Mac OS X 10.5.8. 
     
    5050 
    5151Bundler's manifest file is named 'Gemfiles' and should be created in the project's root directory. 
    52 The manifest file contains a list of gems that are required by your application, along with a series 
    53 of other configuration parameters.   At a minimum, you have to require at least one gem, 
     52The manifest file contains a list of gems that are required by your application, along with an assortment 
     53of other configuration parameters.   At a minimum, you must require at least one gem, 
    5454so start by requiring the 'rails' gem.  To determine which version of that gem to require, examine 
    5555$RAILS_APP_ROOT/config/environment.rb and find a line that looks similar to the following: 
     
    5959}}} 
    6060 
    61 Now, create an initial version of 'Gemfiles' that includes basic configuration options: 
     61Now, create an initial version of 'Gemfiles' that includes some basic configuration information: 
    6262 
    6363{{{ 
     
    8383}}} 
    8484 
    85 This step will likely need to be repeated several times, meaning: I don't know of an easy way to determine the complete list of gems required by any given project unless those gems and their version numbers are already listed somewhere.  Typically what do is 1.) start with a minimal list like the one above, 2.) run through the remainder of this process until I hit a problem (e.g. exceptions encountered while trying to start the rails application, while using the application, or during a gem's installation if something fails to compile because the gem needs additional flags or environment variables to be set). 
     85This step will likely need to be repeated several times, meaning: I don't know of an easy way to determine the complete list of gems required by any given project unless those gems and their version numbers are already listed somewhere else.  Typically what do is 1.) start with a minimal list like the one above, 2.) run through the remainder of this process until I hit a problem (e.g. exceptions encountered while trying to start the rails application, while using the application, or during a gem's installation if something fails to compile because the gem needs additional flags or environment variables to be set), and 3.) add whatever missing gems I find to Gemfiles and repeat the bundling process.  
    8686 
    8787== Create a build options file ==