Rails%203%20In%20Action

404 CHAPTER 14 Deployment
The first line here adds the lib directory of RVM to the load path (represented in Ruby
by $:). This is required so that this file knows where to find rvm/capistrano. Without
it, it may fail.
Now that you’re requiring rvm/capistrano when you run cap deploy again, you’ll
see this additional output just after the stylesheets, javascripts, and images touching:
* executing `bundle:install'
* executing "ls -x /home/ticketeeapp.com/apps/ticketee/releases"
servers: ["your-server"]
[your-server] executing command
command finished
* executing "bundle install --gemfile [release_path]/Gemfile
--path [shared_path]/bundle
--deployment
--quiet
--without development test"
servers: ["your-server"]
[your-server] executing command
command finished
Bundler’s added a bundle:install task to your Capistrano configuration which runs
after deploy:finalize_update. This task runs ls -x command at the beginning to
get the last release’s directory (20110207202618, in this case), which it then uses to
specify the location of the Gemfile using the --gemfile flag passed to bundle
install. Rather than installing the gems to a system location which may not be writable
by this user, 25 Bundler elects to install this to the /home/ticketeeapp.com/apps/
ticketee/shared/bundler directory instead, specified by the --path flag.
The --deployment flag specifies that the repository must contain a Gemfile.lock
file (meaning the gem versions are locked) and that the Gemfile.lock file is up-to-date
according to the Gemfile. This is to ensure that you’re running an identical set of
gems on your server and local machines.
Last, the --without flag tells Bundler what groups to ignore. The development
and test groups are ignored in this case, meaning gems specified in these two groups
will not be installed at all.
With your application’s gems installed, you’re getting even closer to having an
application running. When you deploy changes to your application, these changes
may include new migrations, which will need to be run on the server after you do a
deploy. You can deploy your code and migrate by running this lovely command:
cap deploy:migrations
After your code deploys, Capistrano will run the rake db:migrate task, which is of
great use, because it sets up your database tables. You’ll see output like this:
** [out :: [server]] (in [path_to_application])
** [out :: [server]] == CreateProjects: migrating ===
25 This directory would be located within /usr/local/rvm, which is only writable by members of the rvm group.
This member is not a part of this group and thus is unable to install any gems at a system-wide level.