If you don't have a RubyMotion app yet, generate one. $ motion create myapp $ cd myapp You'll need to create a Gemfile. Here we're using bubblewrap. gem ' bubble-wrap' Then, set up your Rakefile to require your bundled gems at compile time. Add this to the top of the file, right benea...
Bundler adds the ability to use gems directly from git repositories. Setting them up is as easy as adding a gem to your Gemfile. Using the very latest version of a gem (or even a fork) is just as easy as using an official release. Because Rubygems lacks the ability to handle gems from...
Run an executable that comes with a gem in your bundle $ bundle exec rspec spec/models In some cases, running executables without bundle exec may work, if the executable happens to be installed in your system and does not pull in any gems that conflict with your bundle. However, this ...
Now instead of checking out the remote git repository, the local override will be used. Similar to a path source, every time the local git repository change, changes will be automatically picked up by Bundler. This means a commit in the local git repo will update the revision in the G...
That line declares that this application has a dependency on the Ruby VM that is ABI-compatible with 1.9.3. If the version check does not match, Bundler will raise an exception. This will ensure the running code matches. You can be more specific with the
As a result, bundler comes with a --deployment flag that encapsulates the best practices for using bundler in a deployment environment. These practices are based on significant feedback we have received during the development of bundler, as well as a number of bug reports that mostly ...
NAME SYNOPSIS DESCRIPTION BUNDLE INSTALL --BINSTUBS ENVIRONMENT MODIFICATIONS RUBYGEMS PLUGINS bundle-exec(1) bundle-exec(1) NAME bundle-exec - Execute a command in the context of the bundle SYNOPSIS bundle exec command DESCRIPTION This command executes the command, making all gems sp...
NAME SYNOPSIS DESCRIPTION BUILD OPTIONS CONFIGURATION KEYS LIST OF AVAILABLE KEYS LOCAL GIT REPOS bundle-config(1) bundle-config(1) NAME bundle-config - Set bundler configuration options SYNOPSIS bundle config [name [value ]] DESCRIPTION This command allows you to interact with bundle...
Make sure all dependencies in your Gemfile are available to your application. $ bundle install [--system] Gems will be installed to your default system location for gems. If your system gems are stored in a root-owned location (such as in Mac OSX), bundle will ask for your root passwo...
NAME SYNOPSIS DESCRIPTION GIT AND PATH GEMS REMOTE FETCHING 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 vendor/cache...
# setup adds gems to Ruby's load path Bundler.setup # defaults to all groups require "bundler/setup" # same as Bundler.setup Bundler.setup(:default) # only set up the _default_ group Bundler.setup(:test) # only set up the _test_ group (but `not` _default_) Bundler.setup(:default, :tes...
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...
Run an executable that comes with a gem in your bundle $ bundle exec rspec spec/models In some cases, running executables without bundle exec may work, if the executable happens to be installed in your system and does not pull in any gems that conflict with your bundle. However, this ...
