File: bundle-package.txt [bundler-1.3.5 Documentation]

### Home Classes Methods

### Files

- bundle
- bundle-config
- bundle-config.txt
- bundle-exec
- bundle-exec.txt
- bundle-install
- bundle-install.txt
- bundle-package
- bundle-package.txt
- bundle-platform
- bundle-platform.txt
- bundle-update
- bundle-update.txt
- bundle.txt
- gemfile.5.txt
- Executable
- Gemfile

### Class Index

Quicksearch

- Bundler
- Bundler::BundlerError
- Bundler::CLI
- Bundler::Definition
- Bundler::DepProxy
- Bundler::Dependency
- Bundler::Deployment
- Bundler::Deprecate
- Bundler::DeprecatedError
- Bundler::Dsl
- Bundler::EndpointSpecification
- Bundler::Env
- Bundler::Environment
- Bundler::Fetcher
- Bundler::Fetcher::CertificateFailureError
- Bundler::Fetcher::FallbackError
- Bundler::Fetcher::SSLError
- Bundler::GemHelper
- Bundler::GemHelpers
- Bundler::GemInstaller
- Bundler::GemNotFound
- Bundler::GemfileError
- Bundler::GemfileNotFound
- Bundler::GemspecError
- Bundler::GitError
- Bundler::Graph
- Bundler::Graph::GraphVizClient
- Bundler::HTTPError
- Bundler::Index
- Bundler::Injector
- Bundler::InstallError
- Bundler::InstallHookError
- Bundler::Installer
- Bundler::InvalidOption
- Bundler::InvalidSpecSet
- Bundler::LazySpecification
- Bundler::LockfileError
- Bundler::LockfileParser
- Bundler::MarshalError
- Bundler::MatchPlatform
- Bundler::PathError
- Bundler::ProductionError
- Bundler::RemoteSpecification
- Bundler::Resolver
- Bundler::Resolver::SpecGroup
- Bundler::RubyDsl
- Bundler::RubyVersion
- Bundler::RubyVersionMismatch
- Bundler::RubygemsIntegration
- Bundler::RubygemsIntegration::AlmostModern
- Bundler::RubygemsIntegration::Ancient
- Bundler::RubygemsIntegration::Future
- Bundler::RubygemsIntegration::Gem
- Bundler::RubygemsIntegration::Gem::SourceIndex
- Bundler::RubygemsIntegration::Legacy
- Bundler::RubygemsIntegration::Modern
- Bundler::RubygemsIntegration::Transitional
- Bundler::Runtime
- Bundler::SecurityError
- Bundler::Settings
- Bundler::SharedHelpers
- Bundler::SimilarityDetector
- Bundler::Source
- Bundler::Source::Git
- Bundler::Source::Git::GitProxy
- Bundler::Source::Path
- Bundler::Source::Path::Installer
- Bundler::Source::Rubygems
- Bundler::SpecSet
- Bundler::SystemRubyVersion
- Bundler::UI
- Bundler::UI::RGProxy
- Bundler::UI::Shell
- Bundler::VersionConflict
- Gem
- Gem::Dependency
- Gem::Platform
- Gem::Requirement
- Gem::Specification
- Object

No matching classes.

BUNDLE-PACKAGE(1) BUNDLE-PACKAGE(1)

NAME

    bundle-package - Package your needed .gem files into your application

SYNOPSIS

    bundle package

DESCRIPTION

    Copy  all of the .gem files needed to run the application into the ven-
    dor/cache directory. In the future, when running bundle install(1) bun-
    dle-install.1.html, use the gems in the cache in preference to the ones
    on rubygems.org.

GIT AND PATH GEMS

    Since Bundler 1.2, the bundle package command can also package :git and
    :path  dependencies  besides  .gem  files.  This needs to be explicitly
    enabled via the --all option. Once  used,  the  --all  option  will  be
    remembered.

REMOTE FETCHING

    By  default,  if you simply run bundle install(1) bundle-install.1.html
    after running bundle  package(1)  bundle-package.1.html,  bundler  will
    still  connect to rubygems.org to check whether a platform-specific gem
    exists for any of the gems in vendor/cache.

    For instance, consider this Gemfile(5):

        source "https://rubygems.org"

        gem "nokogiri"

    If you run bundle package under C Ruby, bundler will retrieve the  ver-
    sion  of  nokogiri  for the "ruby" platform. If you deploy to JRuby and
    run bundle install, bundler is forced to check to see whether a  "java"
    platformed nokogiri exists.

    Even  though  the  nokogiri  gem  for  the Ruby platform is technically
    acceptable on JRuby, it actually has a C extension that does not run on
    JRuby.  As  a  result,  bundler  will,  by  default,  still  connect to
    rubygems.org to check whether it has a version of one of your gems more
    specific to your platform.

    This problem is also not just limited to the "java" platform. A similar
    (common) problem can happen when developing on Windows and deploying to
    Linux, or even when developing on OSX and deploying to Linux.

    If  you know for sure that the gems packaged in vendor/cache are appro-
    priate for the platform you are on, you can run bundle install  --local
    to  skip  checking  for more appropriate gems, and just use the ones in
    vendor/cache.

    One way to be sure that you have the right platformed versions  of  all
    your gems is to run bundle package on an identical machine and check in
    the gems. For instance, you can run  bundle  package  on  an  identical
    staging  box during your staging process, and check in the vendor/cache
    before deploying to production.

                               April 2013                 BUNDLE-PACKAGE(1)

[Validate]

Generated with the Darkfish Rdoc Generator 2.